Re: Benchmarks for module compilation time

Using strict and warnings doesn't cost that much in terms of startup time.

The load time of strict.pm or warnings.pm isn't very interesting. To get an idea of the impact of using strict.pm, one should measure the load time of a (large) program and/or module with, and without using strict. I still expect to difference to be tiny. The impact of using warnings.pm is harder to measure, due to its runtime effects.

Comment on Re: Benchmarks for module compilation time

Replies are listed 'Best First'.
Re^2: Benchmarks for module compilation time by itub (Priest) on Jul 20, 2005 at 12:48 UTC
I know, that's why I qualified the statement with "in terms of startup time". ;-) Added: ikegami and the Anonymous Monk are right, of course; I misunderstood the parent node.	[reply]
Re^3: Benchmarks for module compilation time by ikegami (Patriarch) on Jul 21, 2005 at 17:17 UTC
That's still ambiguous. You meansured the effect on the module's startup time, but not on perl's startup time for `strict` and `warnings` since the effect varies depending on the script begin loaded.	[reply] [d/l] [select]