Re: PEAR::DB, backends and assertExtension

Markus Fischer wrote: > > 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 ... Yes > > 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? > One thing for me is a run-time error and other thing is that the software dependencies aren't covered so your system doesn't meet the minimal requirements for using the class. Tomas V.V.Cox