Skip Menu |
 

This queue is for tickets about the threads CPAN distribution.

Report information
The Basics
Id: 123747
Status: rejected
Priority: 0/
Queue: threads

People
Owner: Nobody in particular
Requestors: XENU [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Exception objects are obfuscated
Download (untitled) / with headers
text/plain 342b
Show quoted text
> perl -MException::Class=foobar -Mthreads -E '$t = threads->create(sub { foobar->throw } ); $t->join; say $t->error'
Thread 1 terminated abnormally: main=HASH(0x4df6eb0) at -e line 1. [Generic exception] If it's technically impossible to copy the real exception object to the parent thread, then maybe stringifing it would be more sensible?
Download (untitled) / with headers
text/plain 614b
On 2017-11-26 00:25:28, XENU wrote: Show quoted text
> > perl -MException::Class=foobar -Mthreads -E '$t = threads->create(sub > > { foobar->throw } ); $t->join; say $t->error'
> Thread 1 terminated abnormally: main=HASH(0x4df6eb0) at -e line 1. > [Generic exception] > > If it's technically impossible to copy the real exception object to > the parent thread, then maybe stringifing it would be more sensible?
The exception object is returned to the parent: $t->error As such, while I agree the error object is not stringified in the warning message, there isn't a compelling need to modify the existing XS code to do such.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.