Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127190
To: "'Larry Garfield'" <larry@garfieldtech.com>,
	"'php internals'" <internals@lists.php.net>
References: <39597a9c-6854-40c6-a529-32b2b178cb27@app.fastmail.com>
In-Reply-To: <39597a9c-6854-40c6-a529-32b2b178cb27@app.fastmail.com>
Subject: RE: [PHP-DEV] Concept: Lightweight error channels
Date: Sat, 26 Apr 2025 23:59:21 +0300
Message-ID: <003901dbb6ee$15dc1c60$41945520$@glaive.pro>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AQE9iLLDxgfK5qblVycG2tAV8maICrTyw7Kw
Content-Language: lv
From: juris@glaive.pro ("Juris Evertovskis")

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 exceptions? I'm not even trying to argue, I'm
trying to understand. Is it the implementation (bad/expensive performance)?
Semantics? Handling syntax?

I didn't understand the bubbling changes either. What do you mean by
"fatal"? Does it turn the raised "light error" into a real exception? Or
does it turn into an actual error crashing the whole process?

    function div(int $n, int $d): float raises ZeroDivisor
    {
        if (!$d)
            raise new ZeroDivisor;
  
        return $n/$d;
    }

    function inverse(int $x): float
    {
        // does not handle the raise
        return div(1, $x);
    }

    // assuming the above functions are in a lib, can i rescue this using
some trycatch or not?
    inverse($_GET['x']);

And if I don't rescue, am I supposed to see that I passed a bad value to
`inverse`, a bad value to `div` or just that `inverse` failed to handle a
raise?

BR,
Juris