note eyepopslikeamosquito <blockquote> I am messing around with eval since it's cool </blockquote> Block eval (for exception handling) is cool; string eval is ... luke warm. OK, it is fun, but you should try to avoid it in production code. Quoting [merlyn] from [id://405165]: <blockquote> Do not resort to eval-string if other means are available. You're firing up the compiler (slower than almost any other solution), and exposing yourself to hard to debug and hard to secure practices. </blockquote> Update: If you want a second opinion, see <a href="http://perl.plover.com/qotw/e/solution/001">this quiz of the week</a> where MJD states: <blockquote> A good rule of thumb is that unless what you're trying to do is most clearly described as "compile and run arbitrary Perl code", it's probably a mistake to use 'eval' to do it. </blockquote> Somewhat related, symbolic references are also evil, as convincingly demonstrated by MJD in three parts: <a href="http://perl.plover.com/varvarname.html">part 1</a> and <a href="http://perl.plover.com/varvarname2.html">part 2</a> and <a href="http://perl.plover.com/varvarname3.html">part 3</a>. 452015 452015