I can see you feel strongly about this but could you give an explanation as to why this is bad? A link to some reading would suffice although I doubt it will be as memorable as the thought of setting onesself on fire with a flamethrower.
On 11 Mar 2006 17:25:29 -0800, Randal L. Schwartz <[email protected]> wrote: > >>>>> "Ben" == Ben B <[EMAIL PROTECTED]> writes: > > Ben> I haven't fully researched all possible consequences of the proceeding > Ben> code snippet but I have used something similar to it in some of my > Ben> Mason pages with success. > > Ben> perl -e 'use strict;use warnings;my $a="foo";my $b="a";eval "print > \$${b}";' > > Ben> As you can see, strict and warnings stay on. > > And *eval* is even worse. If symbolic refs were shooting yourself in the > foot, using eval for this is setting yourself on fire with a flamethrower. > > No, wrong direction. No cheese. Not even fried cheese-sticks. :) > > Find a solution that doesn't involve doing something to many *named* > variables. Use a hash instead. > > -- > Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 > <[email protected]> <URL:http://www.stonehenge.com/merlyn/> > Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. > See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training! > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Mason-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mason-users
