Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Type of error with STRICT documented as "var.undefined" but implemented as "var.undef" #285

Closed
dboehmer opened this issue Mar 15, 2021 · 2 comments

Comments

@dboehmer
Copy link

I’m working on a proof of concept to implement a more useful STRICT implementation. See #75 (comment)

I found that the type of error generated

I can fix that but do you want to adhere to published documentation or avoid behavior changes?

I actually doubt anyone is using STRICT mode as currently implemented and even more that anyone relies the error type generated.

@abw
Copy link
Owner

abw commented Mar 16, 2021

Thanks for addressing this. I think it's probably better to keep the implementation the same and update the documentation. But I'm happy either way if decide there's a good reason to keep it as per the docs.

@abw
Copy link
Owner

abw commented Jul 26, 2022

I've updated the Manual/Config.pod to change var.undefined to var.undef

@abw abw closed this as completed Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants