Re: Templates in PEAR

On Jun 2, 2004, at 6:21 PM, Joshua Eichorn wrote:

Lukas Smith wrote:

Ah forgot to mention: This is not a double standard. We are just now beginning to enforce a common vision (or even defining this common vision).

I still consider it a double standard, its the good old i got into PEAR in the past so the rules don't apply to but, but they apply to anything new. They should apply to anything in PEAR. why ?

But really my only goal is to have singular modular template infrastructure in PEAR. And i think its base should be a something Pure php, if you want a different syntax you just have a filter on the templates and that converting could either be runtime, or compile time. And then the current template module would just become api wrappers.

Well I don't really understand what your personal goal has to do with existing packages. The four template engines on PEAR are sufficiently different to justify their existence or in any case each of the has been approved in the past. If there is a new rule, fine. You could invite the leads to merge their packages on a mere voluntarily base but we can't, in my opinion, enforce mergers just because. The removal from the public directory should apply only for Zombies and if no other developer volunteers to take the lead. Regards David Costa

-josh -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php