Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:1438 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 23741 invoked from network); 11 May 2003 14:37:59 -0000 Received: from unknown (HELO mailout10.sul.t-online.com) (194.25.134.21) by pb1.pair.com with SMTP; 11 May 2003 14:37:59 -0000 Received: from fwd10.sul.t-online.de by mailout10.sul.t-online.com with smtp id 19Erxb-0006Bw-06; Sun, 11 May 2003 16:37:55 +0200 Received: from baumbart.post.rwth-aachen.de (520072483730-0001@[80.142.175.63]) by fwd10.sul.t-online.com with esmtp id 19ErxY-1t2VcGC; Sun, 11 May 2003 16:37:52 +0200 Reply-to:marcus.boerger@post.rwth-aachen.de Message-ID: <5.1.0.14.2.20030511163708.0367dbe0@mailbox.rwth-aachen.de> X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 11 May 2003 16:37:51 +0200 To: Derick Rethans Cc: Sterling Hughes ,internals@lists.php.net In-Reply-To: References: <1052077704.11371.319.camel@hasele> <5.1.0.14.2.20030504021938.09452980@mailbox.rwth-aachen.de> <1052077704.11371.319.camel@hasele> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Sender: 520072483730-0001@t-dialin.net Subject: Re: [PHP-DEV] exceptions instead of errors From: marcus.boerger@t-online.de ((Marcus =?iso-8859-1?Q?B=F6rger?=)) At 16:23 11.05.2003, Derick Rethans wrote: >On Sun, 4 May 2003, Sterling Hughes wrote: > > > Just a note that I'd really like to see this. One of the great things > > about exceptions will be: > > > > try { > > $m = mysql_connect("localhost", "user", "pass"); > > $sth = mysql_query("select bar from foo", $m); > > while ($row = mysql_fetch_array($sth)) { > > echo $row[0]; > > } > > mysql_close($m); > > } catch (exception $e) { > > echo $e->getMessage(); > > } > > > > This allows you to remove all the nasty if ($conn) could, and move your > > error handling into a singular place. I *really* would like this for > > internal functions. We could also make a new type of exception > > "internalexception," which a user has to specifically catch. This way > > unless you explictly specify that you want to catch an > > internalexception, it will default to just outputting an error message. > >Sounds like a great idea to me! Yes to me, too! I'll change my error2exception thingie to reflect your idea. marcus