I'm not clear on the end user implications of this - how will the
error be presented now?
On Mon, Mar 12, 2012 at 6:27 AM, wrote:
> Author: torsten
> Date: Mon Mar 12 13:27:30 2012
> New Revision: 1299669
>
> URL: http://svn.apache.org/viewvc?rev=1299669&view=rev
> Log:
> Do not stringify $@ upo
On Mon, Mar 12, 2012 at 02:58:05PM +0100, Torsten Förtsch wrote:
> On Friday, 09 March 2012 22:50:33 Niko Tyni wrote:
> > The two usage warnings use constant strings so
> > they seem safe,
>
> They are safe since the "usage" variable is constant and does not contain any
> %-sequences. I do not se
On Friday, 09 March 2012 22:50:33 Niko Tyni wrote:
> The two usage warnings use constant strings so
> they seem safe,
They are safe since the "usage" variable is constant and does not contain any
%-sequences. I do not see the need to fix anything here. What do I miss?
> but I'm afraid I can't te
On Friday, 09 March 2012 22:50:33 Niko Tyni wrote:
> -Perl_croak(aTHX_ SvPV_nolen(ERRSV));
> +Perl_croak(aTHX_ "%s", SvPV_nolen(ERRSV));
Thanks!
But isn't the right way to rethrow/propagate an exception (with respect to
exception objects) this?
Perl_croak(aTHX_ Nullch);
Unles
