Am 06.10.2016 um 21:07 schrieb Brandon Allbery via RT:
> Actually, now that I think about it, there is something that can be done;
> not ideal, but the best we could do under the circumstances. Callbacks
> should be given default exception handlers that at minimum output the
> original exception
Am 06.10.2016 um 21:07 schrieb Brandon Allbery via RT:
Actually, now that I think about it, there is something that can be done;
not ideal, but the best we could do under the circumstances. Callbacks
should be given default exception handlers that at minimum output the
original exception (which
On Thu, Oct 6, 2016 at 1:48 PM, Brandon Allbery via RT <
perl6-bugs-follo...@perl.org> wrote:
> I believe this is known. and it's difficult to fix: you simply can't map
> exceptions across languages, so an exception in a Perl callback from a C
> function called from Perl can only be caught in the
On Thu, Oct 6, 2016 at 1:48 PM, Brandon Allbery via RT <
perl6-bugs-follo...@perl.org> wrote:
> I believe this is known. and it's difficult to fix: you simply can't map
> exceptions across languages, so an exception in a Perl callback from a C
> function called from Perl can only be caught in the
On Thu, Oct 6, 2016 at 1:39 PM, Itsuki Toyota
wrote:
> In the following example, ` my = sub (Int $piyo) ` has wrong
> signature (` my = sub (Int $piyo, Num $fuga) ` is a right one)and
> it returns the error message of "Internal error: Unwound entire stack and
>
On Thu, Oct 6, 2016 at 1:39 PM, Itsuki Toyota
wrote:
> In the following example, ` my = sub (Int $piyo) ` has wrong
> signature (` my = sub (Int $piyo, Num $fuga) ` is a right one)and
> it returns the error message of "Internal error: Unwound entire stack and
>
# New Ticket Created by Itsuki Toyota
# Please include the string: [perl #129820]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=129820 >
In the following example, ` my = sub (Int $piyo) ` has wrong signature (`
my = sub