Front page | perl.perl5.porters |
Postings from July 2023
Thread Previous
|
Thread Next
From:
Alexander Hartmaier
Date:
July 17, 2023 14:52
Subject:
Message ID:
CAB49Qrad0U6dAN6R+pivR09RN_1UXcxqxUYVjAzHsJLTunEJtg@mail.gmail.com
On Sat, Jun 18, 2022 at 2:20â¯AM Ricardo Signes <perl.p5p@rjbs.manxome.org>
wrote:
> On Wed, Jun 8, 2022, at 07:12, Paul "LeoNerd" Evans wrote:
>
> While it is initially tempting to suggest that `catch` would expose
> core-thrown exceptions as objects, there is already a problem here. In
> the past 20-odd years, the $@ variable (and more recently catch) have
> always exposed core-thrown exceptions as plain strings; anything that
> appears as an object must have been some user-thrown object:
>
>
> I believe you eventually came around to agreeing that this made sense.
> "catch ($e)" could get an object in $e, while $@ would remain a string.
> (You did this through the creation of a hypothetical ${^EXCEPTION}, but I
> think it's largely immaterial.)
>
> This likely means that try/catch remain experimental a bit longer, but
> also seems well worth it to me.
>
> --
> rjbs
>
@Ovid: I hope you're lurking around here. I just read your post at
https://www.reddit.com/r/perl/comments/1515tkj/what_do_we_need_for_perl_8/
and wanted you to point here regarding the native exception proposal which
I'm also highly interessted in but wasn't able to accomplish it alone.
Count me in if/when design on it starts!
Thread Previous
|
Thread Next