The following behaviour is observed (i.e. this isn't a guess):
- It compiles and runs. (I consider this a bug.) That's not the case for my argument list expressions that don't constant-fold into a list of simple variables.
- In the sub, $a and $b are declared as lexicals since the values of the package variables aren't used.
my has compile-time actions and run-time actions.
- The compile-time action declares the lexicals.
- The run-time action ensures the lexicals are cleared or replaced on scope exit.
From the observed behaviour, I deduce the following compile-time behaviour:
- When encountering a variable fetch, if parsing the argument list of my, treat it as a variable decleration instead.
- After parsing a my, check if its argument list is a plain variable list. If not, throw an error.
- Constant folding of my's argument list happens before the above check.
That makes
my (0?$a:$b) = 3;
equivalent to
(0 ? (my $a) : my $b ) = 3;
and
my $a if 0;
my ($b) = 3;
(minus the warning).
-
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.
|