Re:Eval() Isn't Quite Pure Evil
by mr_dbr on Tuesday September 08, 2009 @10:42PM
(#812440)
The first bit of code seemed perfectly readable..
Seems like decreasing the font size a few points would have clearer a better solution than clouding the could with loops and `eval()`/closures..
Depending on the context, perhaps showing the first class "full size", and abbreviating the other two would work.. or, show the code for one, then explain "we define another class named C, which prints C, and final one named D, which prints D" - it is a "talk", after all..
That's why I consider `eval` to be "evil" - there's almost always a better way..
Seems like decreasing the font size a few points would have clearer a better solution than clouding the could with loops and `eval()`/closures..
Depending on the context, perhaps showing the first class "full size", and abbreviating the other two would work.. or, show the code for one, then explain "we define another class named C, which prints C, and final one named D, which prints D" - it is a "talk", after all..
That's why I consider `eval` to be "evil" - there's almost always a better way..