> I'm currently writing "The PEAR Manifest", a document that clearly
> defines PEAR once and for all. I'll post the first draft on pear-dev
> here when it's done, but to answer your question, there has been talk
> about a "core" set of packages for a while. In the manifest these are
> called PFC
On Tue, 2002-01-22 at 22:17, Alex Black wrote:
> > Template classes are also foundation components of modern
> > applications.
>
> They are certainly important, but they do not prevent interoperability in
> the same way that different database abstraction packages do.
>
> >> application, using A
Hi Alex,
* Alex Black wrote:
> The database abstraction layer's behavior and capabilities dictate
> application development and we sure as hell don't want 5 abstraction layers
> with the same API floating around.
Why not? People can choose if they want to use PEAR::Metabase
or PEAR::DB or PHPLIB
> * Manuel Lemos wrote:
>> I think that the greatest point of the merger is to have one and only
>> one abstraction layer in PEAR,
>
> I think consensus was that there shouldn't be "the one and
> only XYZ" PEAR class but "more than one XYZ" PEAR class (like
> IT[X] and the PEAR rewrite of PHPLib'
4 matches
Mail list logo
