Re: [phplib] [Fwd: [PHP-PEAR] Merging PHPLIB into PEAR] From: Björn Schotte (bjoern <email protected>)
Date: 01/29/01

* Alexander Aulbach wrote:
> - In real life the "many pages" must be programmed by different
> developpers and they all use other tools and libraries, one uses for
> example PEAR::DB, the other uses pure mysql-API-calls...

That's a problem of discipline. An advanced software
engineer is able to use all the three APIs you mentioned
easily. And if you're disciplined enough, there are
coding guidelines for your project which _tell_ you
which API you _must_ use. No matter if you want to use
it or not.

> Cause every class in PHPLIB is tangled with others, a developer needs some
> days to understand, how he can use PHPLIB to fit all his wishes. In this
> time he also could program it by himself.

That's time waste and not economically. An advanced
software architect who knows about PHP objects will
easily use PHPLIB.
 
> I don't see any difference between PHPLIB local.inc:
> <?
>
> class bla extends DB_Sql
> ...
> class blubb extends DB_Sql...
> doozens lines of code ...
> ...
> ?>
>
> and a configuration file like config.inc
>
> <?
>
> $dbblconnect="mysql://....";
> $dbblubbconnect="mysql://...";
> ...
>
> ?>

I see a difference. The difference about name spacing. Especially
when you've got a team of 5 or 6 people where everyone uses his
own style. 

-- 
Björn Schotte                        b.schotte <email protected>
http://rent-a-phpwizard.de/          bjoern <email protected>

Wishlist: http://www.amazon.de/exec/obidos/wishlist/2SOEML0XDN2R5

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>