comment on

...I personally feel that the mere existence of undefined behavior is a Bad Thing(TM)...

This is why I think that is a bug!

And I don't thin that this is classified as a closure, since the variable is defined in it's own scope, not outside of it. Soo it can't close what it delcare for it self! This is just a persistent scope variable. But in the end is all the same thing. I just don't think that is a closure because it's not stealing a variable from other scope, but from it self.

And I really think that this behavior should be removed, at least we need to start with the warnings from now.

Graciliano M. P.
"Creativity is the expression of the liberty".

In reply to Re: Re: This is really a Perl BUG with my?! Need some advice... by gmpassos
in thread This is really a Perl BUG with my?! Need some advice... by gmpassos

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl: the Markov chain saw
	PerlMonks