Bug #96311 for Moose: Moose::Exception public api

Sat Jun 07 13:17:34 2014 xenoterracide [...] gmail.com - Ticket created

Subject:	Moose::Exception public api
Date:	Sat, 7 Jun 2014 12:17:25 -0500
To:	bugs-moose [...] rt.cpan.org
From:	Caleb Cushing <xenoterracide [...] gmail.com>

firstly, I'd suggest a Role perhaps Moose::Throwable or Moose::Exceptional that provides as much implementation as possible, and composes into Moose::Exception. This role should document the things that are hard/impossible to do in a role and how to accomplish them. This is for cases where it might be a good idea to make an object that can't be further subclassed "throwable" I suggest this role provide a Throwable like interface, with things like a throw method, so that we can do ClassName->throw( message => '...' ); or similar, this is in part due to PBP not liking die, but also so you don't have to create a whole subclass for simple exceptions also a few additional generic exception types might be nice. swapping the implementation of confess (that Moose Exports)' ' that's returned to be synonymous for throwing a Moose::Exception with the message set to the param would be awesome. -- Caleb Cushing http://xenoterracide.com Calendar: https://www.google.com/calendar/embed?src=xenoterracide%40gmail.com&ctz=America/Chicago

Sat Jun 07 14:24:09 2014 xenoterracide [...] gmail.com - Ticket #96314: Ticket created

Subject:	Re: Moose::Exception public api
Date:	Sat, 7 Jun 2014 13:24:00 -0500
To:	bugs-moose [...] rt.cpan.org
From:	Caleb Cushing <xenoterracide [...] gmail.com>

note Business::CyberSource::Response would be able to be thrown if this were possible instead of the existence of Business::CyberSource::Exception::Response (soon to be on CPAN at the time of this writing) On Sat, Jun 7, 2014 at 12:17 PM, Caleb Cushing <xenoterracide@gmail.com> wrote: Show quoted text

> firstly, I'd suggest a Role perhaps Moose::Throwable or > Moose::Exceptional that provides as much implementation as possible, > and composes into Moose::Exception. This role should document the > things that are hard/impossible to do in a role and how to accomplish > them. This is for cases where it might be a good idea to make an > object that can't be further subclassed "throwable" > > I suggest this role provide a Throwable like interface, with things > like a throw method, so that we can do ClassName->throw( message => > '...' ); or similar, this is in part due to PBP not liking die, but > also so you don't have to create a whole subclass for simple > exceptions > > > also a few additional generic exception types might be nice. > > swapping the implementation of confess (that Moose Exports)' ' that's > returned to be synonymous for throwing a Moose::Exception with the > message set to the param would be awesome. > > -- > Caleb Cushing > > http://xenoterracide.com > > Calendar: > https://www.google.com/calendar/embed?src=xenoterracide%40gmail.com&ctz=America/Chicago

-- Caleb Cushing http://xenoterracide.com Calendar: https://www.google.com/calendar/embed?src=xenoterracide%40gmail.com&ctz=America/Chicago

Sun Jun 08 13:28:32 2014 ether [...] cpan.org - Ticket #96314: Merged into ticket #96311

Sun Jun 08 13:28:32 2014 ether [...] cpan.org - Merged into ticket #96311

Tue Jul 01 14:20:36 2014 ether [...] cpan.org - Correspondence added

We now document that Throwable should be used for external exceptions, rather than the Moose::Exception guts (which is just an inlined version of the relevant bits of Throwable, since we don't want a Moo dependency).

Tue Jul 01 14:20:37 2014 The RT System itself - Status changed from 'new' to 'open'

Tue Jul 01 14:20:37 2014 ether [...] cpan.org - Status changed from 'open' to 'resolved'