R: R: [Phplib-users] PEAR versus phplib

[Gaetano G. <giu...@se...>]

> Hello Gaetano,
>=20
> Thursday, September 19, 2002, 5:07:30 PM, you wrote:
> GG> My own wishes:
> GG> - make it compatible with REGISTER_GLOBALS OFF! Either have 2 API
> GG> sets or just dump the old code, I don't mind too much as=20
> long as it is compatible
> GG> with new releases of PHP.
>=20
> Yes, that's too easy. We'll have to dump nothing more than=20
> all the code based upon
> PHPLib as well with the API change :)
>=20

Ok, I know it's not THAT easy. But if phplib is to survive, it has to =
adapt to new versions of the engine.

> GG> - provide alternatives to the db-access layer, e.g.=20
> better integration w. adodb
> GG> or pear-db etc...
> Nothing in PHPLib depends on DB_SQL - one can use the db=20
> abstraction he
> likes. The only thing - if CT_SQL is used, just adapt it to the other
> db API.

Yep, exactly what I've done. What I intended to suggest is to bundle =
with the phplib distro the alternatives to CT_SQL (there are so many of =
them already), so everybody can use them instead of having to rewrite =
from scratch.

>=20
> GG> - provide integration with other php projects that do all=20
> the auth-session over again,
> GG> e.g. phpBB
> As I know, applications are usually built over the libraries, not vice
> versa. And if an app uses its own libraries and apis, there's nothing
> good in adapting other libraries for it - apps will always use the
> libraries they've initially been based upon.
>=20

Just bully (or bribe) the app writers into doing the dirty job!