Date: 07/21/01
- Next message: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Previous message: Jesse Swensen: "Re: [phplib] [RFC] Future of phplib"
- In reply to: Alan T. Miller: "RE: [phplib] [RFC] Future of phplib"
- Next in thread: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Reply: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Reply: Alan T. Miller: "RE: [phplib] [RFC] Future of phplib"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
le 21/07/01 14:45, Alan T. Miller ā amiller <email protected> a écrit :
> like Bjorn, I
> agree that the future will be in PEAR, and see that effort as what ought to
> be the ultimate aim for PHPLib's future if it wants one.
Hi Alan,
As I understand, the purpose of PEAR is to gather many useful classes (Php
Extension Add-on Repository).
I don't see why development with PHPLIB could not be done using also PEAR
classes to manage special functionality. I use PHPLIB with other PEAR
classes all the time.
The future is neither in PEAR or PHPLIB, it is where we put our efforts.
There is a place for both PEAR and PHPLIB, it is just a matter of
positioning. PEAR : heavyweight, powerful but slower - PHPLIB : easier,
faster but not as complete.
Regards
Bertrand Mansion
Mamasam
-- Abbestellen mit Mail an: phplib-unsubscribe <email protected> Kommandoliste mit Mail an: phplib-help <email protected>
- Next message: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Previous message: Jesse Swensen: "Re: [phplib] [RFC] Future of phplib"
- In reply to: Alan T. Miller: "RE: [phplib] [RFC] Future of phplib"
- Next in thread: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Reply: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Reply: Alan T. Miller: "RE: [phplib] [RFC] Future of phplib"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

