Re: Does eval cause that much of a performance hit?

I wholeheartedly empathise ... it rather sounds like you're in a similar situation to myself whereby excessive verbosity and mostly unnecessary comments e.g. comments almost identical to the code, is preferred over readability and elegance. The preference resulting in, IMO, almost impenetrable code e.g....

# Declare the array
@array = ();

# Initialise the array
$array[0] = 'something';
$array[1] = 'something_else'
$array[2] = 'something_more'
.
.
[download]

Note also the, not atypical, lack of strictures.

I've found (the hard way) that the best way to approach it [the problem] is to, initially, find the lowest common denominator - thereafter both advocating education and demonstrating the benefits of the more elegant approach alongside the traditional approach for all to see...

A user level that continues to overstate my experience :-))

Comment on Re: Does eval cause that much of a performance hit? Download Code

Replies are listed 'Best First'.
Re^2: Does eval cause that much of a performance hit? by Anonymous Monk on May 06, 2009 at 12:53 UTC
I've read this thread a few times now, and that doesn't sound like the case at all :) eval EXPR can never be a solution for readability.	[reply]