Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90390
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.46 as permitted sender)
References: <CADZXHp6UA4iH6196vN_U+rLSu1Tw+EazQod2LVgwJ7kkUCTd7Q@mail.gmail.com>
 <CA+kxMuQkV=OP2Wt9V6DnebMoBgy6aUf3NmZTDPo_yXXAG5N=Yw@mail.gmail.com>
 <568FDA4B.60005@gmail.com>
 <CA+kxMuRc=ZZuZqY3hrR=14hBrLfSNJ8E8hUbOvp6xe-eyzGU5Q@mail.gmail.com>
 <568FE92D.4090001@gmail.com>
 <CA+kxMuTCS9B5v_WyTrVo4VVZCkhLH5_=7SjZtAxvcF2wDpNA8g@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Message-ID: <5690073A.1010501@gmail.com>
Date: Fri, 8 Jan 2016 19:00:10 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <CA+kxMuTCS9B5v_WyTrVo4VVZCkhLH5_=7SjZtAxvcF2wDpNA8g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Deprecation of the Error Control Operator (@ symbol)
From: rowan.collins@gmail.com (Rowan Collins)

Dan Ackroyd wrote on 08/01/2016 18:44:
> You're suggesting that we solve a problem in a way that pretty much 
> every other attempt to do has failed.

I'm not sure where you got the idea that I was suggesting anything of 
the sort.


> it's only by
> encountering all of the small problems that you can realise that
> although they are not perfect, exceptions allow much nicer APIs than
> error checking.

I think you've completely misread what I said; here it is for reference:

> I think it would be perfectly reasonable to implement a new file 
> handling API, which behaves like modern PHP (objects, exceptions, etc)

I am advocating *for* the use of exceptions *in that particular case*.


What I was saying, however, is that the question of how fopen() should 
signal failure is not the same question as how PHP should signal 
warnings. Since this discussion was about warnings, I was trying to move 
the discussion away from its focus on one set of APIs.



> If you forget to try/catch an exception it bubble up and fatals your
> program, which is much better than continuing in an unknown error
> state.

You're preaching to the choir here - I know exceptions are absolutely 
the right thing in many cases, and use them lots in my own code.

I also know that they are not suited to every situation, and that "if 
you don't tell me otherwise, I will halt your program" is sometimes 
massive overkill.

I think we're just talking completely at cross-purposes here; I'm not 
entirely sure what you thought I was advocating, but what I was actually 
saying is really simple:

Exceptions are not the right solution to all the places that PHP 
currently has warnings, so a simplified catch statement ("suppress 
Exception") is not the right replacement for the @ operator.

Regards,
-- 
Rowan Collins
[IMSoP]