[Dancer-users] Handling errors: Best Practices for Module extensions and Plugins
gbhat at pobox.com
Wed Dec 15 17:44:19 CET 2010
On Wed, Dec 15, 2010 at 9:48 PM, damien krotkine <dkrotkine at gmail.com>wrote:
> I personnally prefer croak to die, and carp to warn. Ideally, I
> would croak a instance of a dedicated Dancer error class ?
> Something inspired by this :
> Originally, Dancer was using warn and die, and I introduced some croak and
> carp calls. My evil plan was that it would extend itself to any Dancer core
> and plugin code, but I didn't explicitely pushed anything.
> The call has to be made by $designer I guess :)
> On 15 December 2010 16:41, Gurunandan Bhat <gbhat at pobox.com> wrote:
>> I have seen plugins and modules that extend the core (Dancer::Session::X
>> for instance) handle fatal errors in diverse ways: die and croak for one.
>> Are there best practices for die'ing from a use'd module or plugin?
>> Thank you
>> Dancer-users mailing list
>> Dancer-users at perldancer.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Dancer-users