Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:34299
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fuer-et.de from 62.75.137.136 cause and error)
To: internals@lists.php.net
Date: Mon, 31 Dec 2007 14:27:41 +0100
User-Agent: KMail/1.9.7
References: <8697e5310712310328n4c0fa235wb5654178028942bd@mail.gmail.com> <8697e5310712310409u289e643fo5d0b579a4fbd3311@mail.gmail.com> <4778E534.1040506@daylessday.org>
In-Reply-To: <4778E534.1040506@daylessday.org>
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-ID: <200712311427.48682.email@fuer-et.de>
Subject: Re: [PHP-DEV] Re: Exceptions instead of Fatal Error when calling non existent method?
From: email@fuer-et.de (Stefan Walk)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 31 December 2007 13:48:52 Antony Dovgal wrote:
> Changing PHP's behavior in a backward-incompatible way that would affect
> everyone and *forcing everyone* to use exceptions seems to be really bad
> idea, especially taking into account that your problem can be easily solved
> without it.

What exactly is the backwards compatibility break here? Without the change, 
the code simply dies ... if you don't catch the exception, the code simply 
dies ... except you get a backtrace now and can handle the exception if you 
want to.

Regards,
Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHeO5UpPjfcppEficRAng4AJ4v4G+PyT07cQTYupTgKFnOA130yQCeKWYy
E2tzkWAHOmIKDc/CZw7Dtjw=
=ArZH
-----END PGP SIGNATURE-----