Does Parrot have any policy one way or the other on use of these
variables as opposed to their "punctuation variables" equivalents?
For reference: Here's the ack:
[latest] 538 $ ack no_match_vars
config/gen/platform.pm
22:use English qw( -no_match_vars );
Configure.pl
262:use English qw( -no_match_vars );
t/distro/test_file_coverage.t
10:use English qw( -no_match_vars );
t/harness
94:use English qw( -no_match_vars );
kid51
i think of English as a module for beginners--especially those
familiar with awk. i don't encourage programming in an awk dialect on
this project, and i don't encourage programming at the beginner level
on this project, either. count me as against English.
~jerry
And the docs for some such are not far away:
$ perldoc perlvar
/\$\^O
leo - yes, typing this needs escaping, but you knew that already - it's
Perl ;)
Okay, then I'll convert to regular variable in Configure.pl in the
course of refactoring. And then have some of our Phalanx Phoenix Parrot
newbies convert the other files as time permits.
kid51
Task: Eliminate use of English pragma in these locations:
Task: Eliminate use of English pragma in these locations:
[latest] 538 $ ack no_match_vars