Re: RFC on merge of PHPLib and Pear

From: Date: Thu, 08 Mar 2001 08:13:27 +0000
Subject: Re: RFC on merge of PHPLib and Pear
References: 1 2  Groups: php.pear 
Request: Send a blank email to php-pear+get-1716@lists.php.net to get a copy of this message
[Björn Schotte <bjoern@baer.main.de>] > * Chuck Hagenbuch wrote: > > Your argument isn't exactly convincing. Put it this way: I could always > > subclass PEAR's DB_mysql if I wanted to, and supply the parameters in the > > class. Could I use a config file without re-writing phplib's DB_sql, or setting > > the parameters manually after instantiating the object (ugly)? No. > > Repeating again: subclassing is the ground concept of > PHPLIB. There's no need for config files. (Personally, > I don't like config files for elementary things like > Session, Auth etc. which are the ground base of my > application. I like config [files|db|data container] > for the datas my application handles with) Subclassing limits your options to just subclassing. In Chuck's DB_mysql example, runtime configuration gives you one more option. - Stig -- Stig Sæther Bakken <ssb@fast.no> Fast Search & Transfer ASA, Trondheim, Norway

« previous php.pear (#1716) next »