Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62015
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fmethod.com from 209.85.215.170 cause and error)
Message-ID: <944663651AFB476E850E2F1AC1CD51B4@pc>
To: "Ferenc Kovacs" <tyra3l@gmail.com>
Cc: "Leigh" <leight@gmail.com>,
	<internals@lists.php.net>
References: <CAPwsocF=bHLo6CH4iL-7QPsYkLOyB0cA6HHjLHLVHxuQayOmxw@mail.gmail.com><3F2B7A4F937D4FA9A1CE88818CBCEB1D@pc> <CAH-PCH7Hc2O+GFvQWNQ37LKy4LcR7NVhEGCE+aAPH9USufjdvQ@mail.gmail.com>
Date: Fri, 3 Aug 2012 19:36:21 +0300
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0047_01CD71AF.42714F30"
Subject: Re: [PHP-DEV] Why do disabled functions / classes generate a WARNING.
From: sv_forums@fmethod.com ("Stan Vass")

------=_NextPart_000_0047_01CD71AF.42714F30
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable


  a php function/operation can raise more than one warning, how would =
you handle that?
  with exceptions you would only get the first one.
  another issue is that with the current error handling model a call can =
trigger a non-fatal error and still return some data.
  with exeptions you can't do that.
  so changing our internal error handling isn't as easy to start =
throwing ErrorException-s, it would require much more workthan that.


Yes it is a bit more work than that. For example include issues two =
errors on include failure, I mute one of them and turn the other into an =
exception, which is one of the behaviors you've mentioned. There are =
ways to fix everything, but you have to be specific, if you want me to =
be specific as well.

Either way I'm trying to give a practical solution you can implement =
today. Aside from practicality, I do also support the idea that =
accessing disabled symbols should be a fatal error, not a warning.

Stan
------=_NextPart_000_0047_01CD71AF.42714F30--