|
Re: Precedence of qw
by dave_the_m (Monsignor) on Apr 04, 2006 at 19:12 UTC
|
This was fixed in perl 5.8.8:
$ perl587 -wle 'print for qw(X Y) x 2'
Unquoted string "x" may clash with future reserved word at -e line 1.
Number found where operator expected at -e line 1, near "x 2"
(Do you need to predeclare x?)
syntax error at -e line 1, near "qw(X Y) x "
Execution of -e aborted due to compilation errors.
$ perl588 -wle 'print for qw(X Y) x 2'
X
Y
X
Y
$
Dave. | [reply]
[d/l] |
|
|
| [reply]
[d/l]
[select] |
|
|
| [reply] |
Re: Precedence of qw
by diotalevi (Canon) on Apr 04, 2006 at 16:30 UTC
|
x doesn't play by normal rules and will do things slightly funny just because the qw() used parens instead of some other delimiter. So x's special handling are higher priority just because it's special. You shouldn't infer much from it. This is likely all very implementation specific too so it could change.
| [reply]
[d/l]
[select] |
|
|
use warnings;
@array = qw!X! x 2;
print @array, "\n";
gives
Unquoted string "x" may clash with future reserved word at 541179.pl l
+ine 2.
Number found where operator expected at 541179.pl line 2, near "x 2"
(Do you need to predeclare x?)
syntax error at 541179.pl line 2, near "qw!X! x "
Execution of 541179.pl aborted due to compilation errors.
| [reply]
[d/l]
[select] |
Re: Precedence of qw
by ikegami (Patriarch) on Apr 04, 2006 at 16:33 UTC
|
Your greeting implies the problem is related to use strict, but it isn't.
use warnings;
@array = qw(X) x 2;
print @array, "\n";
gives
Unquoted string "x" may clash with future reserved word at 541178.pl l
+ine 2.
Number found where operator expected at 541178.pl line 2, near "x 2"
(Do you need to predeclare x?)
syntax error at 541178.pl line 2, near "qw(X) x "
Execution of 541178.pl aborted due to compilation errors.
I've noticed this bug before.
| [reply]
[d/l]
[select] |
|
|
Sorry about that; it wasn't my intent.
I noticed something else that I posted. This:
#!/usr/bin/perl -w
use strict;
my $scalar = qw(A B C);
print $scalar, "\n";
Gives:
Use of implicit split to @_ is deprecated at ./test27.pl line 4.
3
And perldiag has:
Use of implicit split to @_ is deprecated
(D deprecated) It makes a lot of work for the compiler when you clobber a subroutine's argument list, so it's better if you assign the results of a split() explicitly to an array (or list).
I'm not sure how these are related... | [reply]
[d/l] |
|
|
Your version of perl probably implements
qw(A B C)
as
split(' ', q(A B C))
(although I suspect it performs said split at compile-time).
Given the above, consider the following passage from split's documentation:
In scalar context, returns the number of fields found and splits into the @_ array. Use of split in scalar context is deprecated, however, because it clobbers your subroutine arguments.
If you want the count, use my $scalar = () = qw(A B C);.
By the way, I said "your version of perl" because perl 5.6.1 gives
Useless use of a constant in void context at 541192.pl line 4.
Useless use of a constant in void context at 541192.pl line 4.
C
| [reply]
[d/l]
[select] |
|
|
|
|
| [reply] |
|
|
|
|
|
|
$ perl -w
use strict;
my $scalar = qw(A B C);
Useless use of a constant in void context at - line 3.
Useless use of a constant in void context at - line 3.
print $scalar, "\n";
C
$ perl -v
This is perl, v5.8.7 built for cygwin-thread-multi-64int
(with 1 registered patch, see perl -V for more detail)
By the way, this has nothing to do with qw.
$ perl -w
my $scalar = (1, 2, 3);
Useless use of a constant in void context at - line 1.
| [reply]
[d/l]
[select] |
Re: Precedence of qw
by doc_faustroll (Scribe) on Apr 04, 2006 at 17:03 UTC
|
seems like you are getting too complicated and choosing the wrong operator here. Tell me why you want to use the qw operator?
from perldoc perlop
qw/STRING/
Evaluates to a list of the words extracted out of STRING, using
embedded whitespace as the word delimiters. It can be under-
stood as being roughly equivalent to:
split(’ ’, q/STRING/);
the differences being that it generates a real list at compile
time, and in scalar context it returns the last element in the
list.
So why in the heck would you use this operator on one value in the middle of a push statement. The interpreter does its best but you are making it hemmorage here. use the q operator.
#This works:
push @array, q(X) x 2;
print @array, "\n";
| [reply]
[d/l] |
|
|
doc,
I was looking at qw() for maintenance purposes; so some one would be able to type in a new word if need be instead of the extra comma, quote, quote--Yes, picky, I know. But, again, this is used a lot in Perl to allow for easy modification.
Your code will not work because q(X) x 2 results in ('XX') not ('X', 'X') as you can see via:
#!/usr/bin/perl -w
use strict;
my @array;
push @array, q(X) x 2;
print join ' - ', @array, "\n";
@array = ();
push @array, ('X') x 2;
print join ' - ', @array, "\n";
| [reply]
[d/l] |
|
|
(q(X)) x 2 would give ('X', 'X')
| [reply]
[d/l]
[select] |
|
|
aha. I see. thanks.
although if you are using single words?
I can see the need for a list context with a list of things.
anyhoo, glad the fix is in release, and my compliments to you for a clever username. one of the more clever ones on perlmonks.
| [reply] |