-
Notifications
You must be signed in to change notification settings - Fork 47
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
strange lack of warnings #51
Comments
Yes, any operation on nil(undef) says nothing by default while <: $title.unknown_method :> complains warnings. You can change this behavior by setting Should |
both type of warnings "Use of nil to print" and "Use of nil to invoke method foo" will be raised using verbose => 2 but while "Use of nil to print" is pretty common (I don't want to initialize all my values $value //= ""), calling methods on undef values just seem wrong and much less common so both type of warnings might be activated on different levels? |
Sure. I will change the level of two warning types as:
Thanks to the suggestion. |
thanks, hope this helps to make debugging a bit easier (as the old behavior produced some hard to find bugs at least in my use cases :) |
@gfx "Sure. I will change the level of two warning types as:" Has it been changed? |
the following code does not provide any warnings -> method call on undef value
is this expected behaviour?
The text was updated successfully, but these errors were encountered: