sub m {} should be illegal

I had considered saying something like that in And i learned never to name my subroutines s but then i realized that &s($n,$k) probably would not have thrown the error.

Well it's a parsing problem, if you manage to enter a subroutine named s into the stash you can certainly call it with &s (which is not a bare word anymore)

Can't test at the moment, and Perl's parser is known to be complicated. :)

(I remember that CGI renamed tr to TR for this reason)

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!}

> if you manage to enter a subroutine named s into the stash you can certainly call it with &s

to illustrate what I meant, *s and &s are not "bare" because of the sigils.

But a bare word s is supposed to start a s/// resp. s()() or s{}{} or ... depending on whatever character follows (even with empty space in between)

This makes parsing particularly difficult.

use strict;
use warnings;


*s = sub { warn "s called" };

&s();

#  --- not working
# sub s {
#   warn "s called"
# }

# --- neither
#   s();
[download]

s called at c:/tmp/pm/s_sub.pl line 11.
[download]

This problem should apply for all perlop#Quote-and-Quote-like-Operators .

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!}