I have a feeling I asked this before, but cannot find the post.
[info] Exception powered by Catalyst 5.90030
What's the reasoning that chained actions continue to run after an earlier
exception?
sub start : Chained( '/' ) : CaptureArgs(0) {
warn in start\n;
}
sub middle : Chained( 'start'
On 05/09/2013 03:25 PM, Bill Moseley wrote:
I have a feeling I asked this before, but cannot find the post.
[info] Exception powered by Catalyst 5.90030
What's the reasoning that chained actions continue to run after an
earlier exception?
sub start : Chained( '/' ) : CaptureArgs(0) {
On Thu, May 9, 2013 at 7:25 AM, Lukas Thiemeier
spamcatc...@thiemeier.netwrote:
On 05/09/2013 03:25 PM, Bill Moseley wrote:
I have a feeling I asked this before, but cannot find the post.
[info] Exception powered by Catalyst 5.90030
What's the reasoning that chained actions continue to
On Thu, May 9, 2013 at 8:31 AM, Bill Moseley mose...@hank.org wrote:
Hi Bill,
This is because you don't want Catalyst to die. Imagine you are running
a fastcgi server and you accidentally created an action which dies on
certain user input.
Hi Lukas,
Sorry, you missed the point. Yes,
On Thu, May 9, 2013 at 9:34 AM, Aristotle Pagaltzis pagalt...@gmx.dewrote:
* Bill Moseley mose...@hank.org [2013-05-09 15:30]:
What's the reasoning that chained actions continue to run after an
earlier exception?
Seems like an accident of the design to me, borderline bug.
Agreed. Seems
Blast from the past:
http://grokbase.com/t/sc/catalyst/077e7jhw9g/rfc-catalyst-plugin-errorout
On Thu, May 9, 2013 at 1:42 PM, Bill Moseley mose...@hank.org wrote:
On Thu, May 9, 2013 at 9:34 AM, Aristotle Pagaltzis pagalt...@gmx.dewrote:
* Bill Moseley mose...@hank.org [2013-05-09
