Disk I/O is usually a bottleneck. eval seems like it'd be faster, but the only way to be sure is to Benchmark your particular application.
Would it be easier still to throw around subroutine references and avoid either step altogether?
In reply to Re: require vs eval
by chromatic
in thread require vs eval
by antirice
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |