in reply to For vs. Foreach

Can you offer a code example where for and foreach behave differently?

(And if you can do so, you might wish to use perlbug to report the bug that causes them to differ...)

Replies are listed 'Best First'.
Re^2: For vs. Foreach
by JavaFan (Canon) on Feb 13, 2009 at 18:04 UTC
    Peeking in toke.c suggests there is one difference between 'for' and 'foreach'. It seems it's valid to use 'for' somewhere in an attribute declaration. The documentation about attribute doesn't make it clear to me how. Best thing I can do is generating different error message when using 'for' or 'foreach': 
    $ perl -wE 'sub foo: foreach'
Invalid CODE attribute: foreach at -e line 1
BEGIN failed--compilation aborted at -e line 1.
$ perl -wE 'sub foo: for'
syntax error at -e line 1, next token ???
Execution of -e aborted due to compilation errors.

    [download]
    Using 'for' is a compile time error, using 'foreach' a run time error (resulting in abortion of the compilation).

    If someone could show how to use 'for' inside an attribute, that would be dandy.

[reply]
[d/l]
      You're right! 
      use Attribute::Handlers;

sub foreach :ATTR {
  print "Just another Perl hacker,\n";
}

sub foo :foreach {}

foo();

      [download]
      prints the expected, while 
      use Attribute::Handlers;
sub for :ATTR {
  print "Just another Perl hacker,\n";
}
sub foo :for {}
foo();

      [download]
      does not. I'll follow my own advice and send a perlbug.
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom