Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83784
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.178 as permitted sender)
Message-ID: <54EDCBD6.70302@gmail.com>
Date: Wed, 25 Feb 2015 13:19:18 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAF+90c-7w1fLqmffYvPRhmtt8rzESEpSmW8vfMD-YfLt1mG_8w@mail.gmail.com> <CAGa2bXaxs760ZVGharG2zZizh-+f4S+kiLv5uH4+UeDFZ4rpkA@mail.gmail.com> <54E12349.7070806@gmail.com> <16.9B.05176.AE1C1E45@pb1.pair.com> <54E1C993.1070609@gmail.com> <37.20.01961.31113E45@pb1.pair.com> <54E32CAA.5030600@gmail.com> <C2.98.18888.BEE64E45@pb1.pair.com> <54E4FAC2.7060200@gmail.com> <E9.64.22021.0E6A5E45@pb1.pair.com> <CA+9eiLu634OpuXVT8NnwZwitqc=S4g8UbbMj+coB4nmQcPXRQQ@mail.gmail.com> <47.89.25547.DD007E45@pb1.pair.com> <op.xuco5eutc9evq2@nikita-pc> <A2.64.08895.E0958E45@pb1.pair.com>
In-Reply-To: <A2.64.08895.E0958E45@pb1.pair.com>
Content-Type: text/plain; charset=koi8-r; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Exceptions in the engine
From: rowan.collins@gmail.com (Rowan Collins)

Tony Marston wrote on 21/02/2015 10:08:
> ""Nikita Nefedov""  wrote in message news:op.xuco5eutc9evq2@nikita-pc...
>>
>> On Fri, 20 Feb 2015 12:39:33 +0300, Tony Marston 
>> <TonyMarston@hotmail.com> wrote:
>>>
>>> I disagree. Exceptions were originally invented to solve the 
>>> semipredicate problem which only exists with procedural functions, 
>>> not object methods. Many OO purists would like exceptions to be 
>>> thrown everywhere, but this would present a huge BC break. If it 
>>> were possible get these functions to throw an exception ONLY when 
>>> they are included in a try ... catch block then this would not break 
>>> BC at all.
>>>
>>
>> Tony, first of all - this still breaks BC, because exception is being 
>> thrown in a place where it used not to be...
>
> I disagree. The following function calls would not throw exceptions
>    fopen(...);
>    fwrite(...);
>    fclose(...);
>
> while the following code would:
>    try {
>        fopen(...);
>        fwrite(...);
>        fclose(...);
>    } catch (....) {
>        ....
>    } 

But what about this code, which could well already exist:

    try {
        $fh = fopen(...);
        $this->processLotsOfDataAndMaybeThrowAnException($fh);
        fclose($fh);
    } catch (....) {
        ....
    }

If fopen() starts throwing exceptions here, that's as much a BC break as 
it throwing them everywhere. If it doesn't, the rules for when it should 
throw become even more complicated, and useful in even fewer cases.

Regards,
-- 
Rowan Collins
[IMSoP]