Neat little trick. I didn't realize you could tie entities to package main, though I don't see why not, and your demonstration shows there's nothing preventing it from being done.
The no warnings qw/syntax/; line seems unnecessary. Is there a reason for it?
I wasn't able to find anything that looked particularly questionable about the code, and running with full warnings it didn't produce any complaints. I'm running Perl version 5.8.2 for Win32. Is there an issue with warnings under other versions? ...just curious.
Also, out of curiosity, what advantage is there to implementing a tied hash in this situation as opposed to a tied scalar?
Update: Trying to answer my own question I did re-implement your solution with simple tied scalars, and found no functional difference, so I assume that the choice to tie a hash was either habbit, or based on something that hasn't occurred to me.
Again, loved the trick.
| [reply] [d/l] |
The no warnings qw/syntax/; line seems unnecessary. Is there a reason for it?
For this program, that line doesn't serve any purpose. But then, neither do the two lines above - yet you aren't inquiring about them. The first six lines are generated
whenever I type ^A-P (two chars), and I don't bother
to remove the last line if it happens to occur in a program
where it's unnecessary.
Trying to answer my own question I did re-implement your solution with simple tied scalars, and found no functional difference,
The fact that the entire word is replaced with identical characters didn't strike you as a functional difference?
In this specific case, you could get away with using tied
scalars if you also used /e, but if letters had
to be replaced with a random letter enclosed in parenthesis, using a tied has would lead to:
s/(\w)/($h{$1})/g;
while you would need something like:
s/(\w)/"($s)"/eg;
which, while it has less characters, is less obvious, IMO.
Abigail | [reply] [d/l] [select] |