Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62060
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <501F46BE.4040407@sugarcrm.com>
References: <CAH-PCH7874id459NTuMqL6pzL=feRtaWUAiPiSqPDa73tnFy9w@mail.gmail.com>
	<501F46BE.4040407@sugarcrm.com>
Date: Sun, 5 Aug 2012 22:33:30 -0600
Message-ID: <CAFMT4NqUVF-Q_TZ_toe_7NCgYBU3J02eVWp46wf=CYRyouWdNg@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Ferenc Kovacs <tyra3l@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Error handling brainstorming
From: morrison.levi@gmail.com (Levi Morrison)

> . . .For example, if you try to
> open a file and the file isn't there, throwing exception is a very
> annoying behavior (yes I know some languages do that, IMO it's wrong).

Because checking that the returned variable is `!== FALSE` is *way*
better than throwing an exception, right?

This type of thing is one of the main reasons I like PDO more than
MySQLi.  In MySQLi I'm constantly checking return values.  In PDO I
just wrap it all up one try/catch.  It's not like if my query fails
I'm going to try a different one.  Most of the time it's just logging
that something went wrong and reporting it upstream somehow.

I understand that opening a file is a bit different than querying a
database, but I have to disagree with your entire previous post.
Exceptions are much nicer than errors.

Of course, everyone is entitled to have and express their own opinion.
I'm just sharing mine.