> >
> > On top of this, there's an argument that you're not addressing: most 
> > template engines in PHP either directly consume PHP template files...
> > or "compile" templates into... PHP template files. As such, sooner or 
> > later, you'll have a class that includes a PHP template file, and 
> > that's where things break for me in this proposal.
> >
>
> They don't break because nobody in their right mind would ever try to
> include a .phpp file in a framework like that.  If its stack is so entangled,
> the very notion of a pure PHP stack is just incompatible.  So your best bet
> on a framework like that would be to stick with .php.

Um, so if you aren't using any form of template engine whatsoever, what are you 
proposing? You're saying we should all go back to the good ol' C days of trying 
to put together valid markup using string concatenation? (Or worse, 
manipulation of DOM classes?) No thanks. IMO this is a bit like blowing up 
London to stop a jaywalker.

After a lot of thought I've decided that I'm strongly opposed to the nature of 
this proposal at a fundamental level. It isn't that I just wouldn't use it. 
This proposal is inherently destructive to the PHP development community. This 
effectively attempts to split PHP into two languages. Current PHP isn't really 
compatible with the proposed ".phpp" version of PHP, in the sense that you 
can't safely use both in the same code base. Unfortunately this will not be 
clear to anybody at first, which will lead to mass proliferation of .phpp 
libraries which are like poison to any unsuspecting PHP user foolish enough to 
try to use one. This isn't just a BC thing, it is really a permanent language 
fork.

John Crenshaw
Priacta, Inc.


--
I am using the free version of SPAMfighter.
We are a community of 7 million users fighting spam.
SPAMfighter has removed 839 of my spam emails to date.
Get the free SPAMfighter here: http://www.spamfighter.com/len

The Professional version does not have this message


--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to