We can discuss whether this optimization is premature or not...
No, we can't. I never saw a profile, neither before nor after. All I saw was a silly knee-jerk argument that "OMG CARP IS TEH SLOOOOOOOW!" and a bunch of patches that added code that perl has to read from the disk, compile, and keep around in memory. There's absolutely no debate possible about whether this was a premature optimization.
Any "optimization" without measurement is premature.
It seems to me that if Ilya Zakharevich never send his optimization patches, then Perl could be as slow as Java...
I don't know what that has to do with this subject, but I've achieved several very measurable optimizations by removing code and almost none by adding code.
In reply to Re^5: evil code of the day: global stricture control
by chromatic
in thread evil code of the day: global stricture control
by ysth
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |