Re: PEAR::DB, backends and assertExtension

From: Date: Sun, 14 Oct 2001 15:43:52 +0000
Subject: Re: PEAR::DB, backends and assertExtension
References: 1 2 3 4  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-2285@lists.php.net to get a copy of this message
On Sun, Oct 14, 2001 at 05:30:46PM +0200, Tomas V.V.Cox wrote : > Markus Fischer wrote: > > > > On Sun, Oct 14, 2001 at 01:22:44AM +0200, Stig S. Bakken wrote : > > > No you haven't overseen anything, so feel free to make it > > > suff^H^H^H^Hconsistent :-) > > > > Ok, but this would mean to change DB::assertExtension *not* to > > call trigger_error(). This is redundant because an meaningfull > > error object is passed back. > > > > Everyone feeling fine with this? > > > > Not me, but think that is too late :-) I liked that Pear DB dies when > the supported isn't compiled in. Are you serious? I mean, really ... > DB::assertExtension, instead we need a common assertExtension method > (for example in PEAR.php). Thats ok. There's nothing from my view against moving DB::assertExtension to PEAR::assertExtension. But do _not_ change its behaviour. What is a library of use when you can't recover gracefully from errors because it just dies? - Markus -- Markus Fischer, http://guru.josefine.at/~mfischer/ EMail: mfischer@guru.josefine.at PGP Public Key: http://guru.josefine.at/~mfischer/C2272BD0.asc PGP Fingerprint: D3B0 DD4F E12B F911 3CE1 C2B5 D674 B445 C227 2BD0 -All your scripts are belong to Zend-

« previous php.pear.dev (#2285) next »