Re: [PHP-PEAR] RFC on merge of PHPLib and Pear

On Wed, Mar 07, 2001 at 07:54:26AM -0500, Jeffrey A. Stuart wrote:

> 2) Underneath that, import ALL of the PHPLib classes into it.
> 3) Initial Pearize of the phplib classes... (IE PHPDoc/style changes to
> functions/var names).

If you're going to import all of the PHPLIB code into PEAR and rewrite
it to PEAR conformance, you're going to break the PHPLIB API.  You
might as well skip that step and just import the pieces of PHPLIB into
PEAR where they belong permanently.

There's really no point in "temporarily" moving the PHPLIB code into
PEAR.  It will just confuse people that will end of relying on it
being under PEAR/PHPLIB/.

> 4) Start moving things around. :)  IE for example, probably move the Auth
> stuff from PHPLib into an Pear::Auth class.

I will most definitely oppose any "moving".  If we already have an
idea where the class should go, why don't we just put it there from
the beginning?

> 7) Write wrappers around the newly moved classes to behave as the old phplib
> classes.

Ugh.  Wrappers are nasty and unnecessary.  If people still have legacy
PHPLIB code in use, they're better of continuing their use of PHPLIB
(IMHO).
 
-- 
Jon Parise ([email protected])  .  Rochester Inst. of Technology
http://www.csh.rit.edu/~jon/  :  Computer Science House Member