develooper Front page | perl.perl5.porters | Postings from June 2022

Re: $@ alternative WAS Re: Core exception types [was: Re: Pre-RFC: Improve “wide character” warnings]

Thread Previous | Thread Next
From:
Karen Etheridge
Date:
June 9, 2022 02:18
Subject:
Re: $@ alternative WAS Re: Core exception types [was: Re: Pre-RFC: Improve “wide character” warnings]
Message ID:
CAPJsHfBuCHHvid37xT+mYt9_DvKwzwVkL+muo1Y3KsmsSdqQ8Q@mail.gmail.com
On Wed, Jun 8, 2022 at 12:56 PM Dan Book <grinnz@gmail.com> wrote:

> Whenever $@ is populated, the relevant logic would check to see if the
>> active feature set dictates putting the object or the string into $@.
>>
>
> This is exactly the problem. The lexical feature would have an effect on
> the exact problematic code we are discussing (which is by the way not
> "esoteric" in any useful sense of the word, we simply cannot break it),
> which is not in the scope of the feature.
>

If I'm following correctly, we want the *caller* of the exception-throwing
code to decide whether it wants an error string or an error object.
Therefore, make $@ into a dualvar-like construct that holds both pieces of
information, and use the context of the caller to decide which form is used
in an expression containing $@.

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About