Hi folks. In several recent RFCs and related discussion, the question of error
handling has come up. Specifically, the problem is:
* "return null" conflicts with "but sometimes null is a real value" (the
validity of that position is debatable, but common), and provides no useful
information a
On Sat, Apr 26, 2025, at 3:59 PM, Juris Evertovskis wrote:
> Hi,
>
> Reading this as a PHP dev is confusing (terminology-wise) because errors
> used to be the fatal ("stop the world") conditions while exceptions were the
> catchable, recovarable issues within some call - feels to me pretty
> equiva
On Sat, Apr 26, 2025, at 11:19 AM, Rob Landers wrote:
> Hey Larry,
>
> I’m still digesting this, but I wonder if this problem (errors vs
> non-world-ending errors vs happy path) is a problem due to people often
> making warnings into exceptions?
>
> I feel like many devs/frameworks “abuse” (for
Hi,
Reading this as a PHP dev is confusing (terminology-wise) because errors
used to be the fatal ("stop the world") conditions while exceptions were the
catchable, recovarable issues within some call - feels to me pretty
equivalent to what you're proposing here.
What's the problem with PHP excep
On Sat, Apr 26, 2025, at 09:17, Larry Garfield wrote:
> Hi folks. In several recent RFCs and related discussion, the question of
> error handling has come up. Specifically, the problem is:
>
> * "return null" conflicts with "but sometimes null is a real value" (the
> validity of that positio
> What's the problem with PHP exceptions? I'm not even trying to argue, I'm
> trying to understand. Is it the implementation (bad/expensive performance)?
> Semantics? Handling syntax?
Larry provided several problems in the opening of his email; you may
want to reread that.
I will affirm that exce
