>>>>> "MJD" == Mark J Dulcey <[EMAIL PROTECTED]> writes:
MJD> Kripa Sundar wrote: >> I could think of three problems with eval(), and replied to him with >> the three points below. Please let me know if I have gotten anything >> wrong below. Also, if you can think of more eval() concerns, please >> help me learn. TIA. MJD> I think you've pretty well covered the ground there; I can't think of MJD> any more issues. Using eval() when you don't need it is like using a MJD> club when a flyswatter will do. It's a nice tool to have when you really MJD> do need a club, but best reserved for only those times. i second that. using a more powerful tool than needed is a bad programming practice. he will jump to using eval since he doesn't seem to care about his code quality. another bad point about eval is that it can access and modify lexicals and globals anywhere in the code. so that can lead to action at a distance and very hard to find bugs. send a copy of perl best practices to him and watch his eyeballs hit the floor when he sees how many other of damian's rules he is breaking. :) uri -- Uri Guttman ------ [EMAIL PROTECTED] -------- http://www.stemsystems.com --Perl Consulting, Stem Development, Systems Architecture, Design and Coding- Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
