Re: [perl #42329] Carp::croak() replace user error message by own

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.

• Re: [perl #42329] Carp::croak() replace user error message by own by Alex Efros
• Re: [perl #42329] Carp::croak() replace user error message by own by Rafael Garcia-Suarez
• Re: [perl #42329] Carp::croak() replace user error message by own by Rafael Garcia-Suarez
• Re: [perl #42329] Carp::croak() replace user error message by own by Dave Mitchell
• Re: [perl #42329] Carp::croak() replace user error message by own by Jim Cromie
• Re: [perl #42329] Carp::croak() replace user error message by own by Nicholas Clark
• Re: [perl #42329] Carp::croak() replace user error message by own by Jim Cromie
• [perl #42329] [PATCH] Carp::croak() replace user error message by own by Bram via RT
• [perl #42329] Carp::croak() replace user error message by own by Bram via RT