>> 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. > By extension, this also applies to Config ?Thread Previous | Thread Next