I would have to agree with Maclir's comments: the syntax as it stands is readable, and that's a good thing. But, if you really want to be clever about it...
As I relearned* last week with this question, you can directly manipulate the symbol table to assign a sub to the CODE portion of a typeglob:
*desiredSubroutineName = sub { ... };
Here's a working example that surprised me:
perl -e '*s1=sub{&s2};*s2=sub{print"Hello,Daniel\n"};&s1'
Unfortunately, that pesky sub-word keeps coming up! :-)
I think the statement about "cleverness" in tilly's reply to my earlier question would be relevant here... I'm guessing that a good portion of the time, most Perl programmers don't (and shouldn't) muck around with the symbol table.
* I said "relearned" in the sense that I had read about this in the Camel, but had never used it.
In reply to Re: A subroutine is a reference to a list of statements
by t'mo
in thread A subroutine is a reference to a list of statements
by princepawn
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |