[Mason-devel] rethrow_exception: $@ garbled

[Dave Rolsky]

I'm curious if anyone noticed the fact that rethrow_exception that is
called from Mason $SIG{__DIE__} doesn't care about $^S, which results in
a patch, which is trivial (return if $^S) but I'd like to know if there
are reasons why it is not done already.

I don't think there's any reason it's not a done. A patch with a test
would be ideal.


-dave

/*===================================================
VegGuide.Org www.BookIRead.com
Your guide to all that's veg. My book blog
===================================================*/

[Dmitry Karasik]

ok, patch and new test are attached. hope these are ok!

/dk

btw, mailing list at sourceforge is sort of broken, doesn't
allow me to send from my domain:

<mason-***@lists.sourceforge.net>: host
externalmx-1.sourceforge.net[12.152.184.25] said: 451-Could not complete
sender verify callout 451-Could not complete sender verify callout for
<***@tetsuo.karasik.eu.org>. 451-The mail server(s) for the domain may be
temporarily unreachable, or 451-they may be permanently unreachable from
this server. In the latter case, 451-you need to change the address or
create an MX record for its domain 451-if it is supposed to be generally
accessible from the Internet. 451 Talk to your mail administrator for
details. (in reply to RCPT TO command)

I think they don't like hosts with graylisting enabled, someone should talk
to sourceforge mail staff possibly.

Post by Dave Rolsky

I'm curious if anyone noticed the fact that rethrow_exception that is
called from Mason $SIG{__DIE__} doesn't care about $^S, which results in
a patch, which is trivial (return if $^S) but I'd like to know if there
are reasons why it is not done already.

I don't think there's any reason it's not a done. A patch with a test
would be ideal.
-dave
/*===================================================
VegGuide.Org www.BookIRead.com
Your guide to all that's veg. My book blog
===================================================*/

[Dmitry Karasik]

Hello,

I'm curious if anyone noticed the fact that rethrow_exception that is called
from Mason $SIG{__DIE__} doesn't care about $^S, which results in nasty garbled
$@ when die is (legitimately) issued inside eval? I'd send a patch, which is
trivial (return if $^S) but I'd like to know if there are reasons why it is not
done already.

[Dmitry Karasik]

Hello,

I'm curious if anyone noticed the fact that rethrow_exception that is called
from Mason $SIG{__DIE__} doesn't care about $^S, which results in nasty garbled
$@ when die is (legitimately) issued inside eval? I'd send a patch, which is
trivial (return if $^S) but I'd like to know if there are reasons why it is not
done already.