Front page | perl.perl5.porters |
Postings from July 2009
2009/6/29 Rafael Garcia-Suarez <rgarciasuarez@gmail.com>: > 2009/6/29 Alex Efros <powerman@powerman.name>: >> Only I can do is try to explain again: error-reporting code like Carp MUST NOT >> request additional resources - because if some error happens it's very >> likely 'not enough resources' error and trying to get more resources just >> to show error message just feels wrong. >> >> I think correct solution will be to load Carp::Heavy together with Carp. >> I see no reason to delay loading Carp::Heavy - it's very small and >> shouldn't affect performance. Moreover, if you wanna speedup Carp loading, >> then there a lot of other techniques - like moving POD to the bottom of >> file under __END__. Also consider just moving Carp::Heavy content to Carp, >> this shouldn't increase Carp module load time by any noticeable value and >> also allow to do some code cleanup. > > I tend to concur. Those days we have more CPU and memory resources, so > a cleanup to merge Carp::Heavy in Carp is totally feasible. This is now done in blead. There's still a Carp::Heavy placeholder for legacy code that wants to force its loading (like File::Temp.)Thread Previous | Thread Next