Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59901
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain priacta.com designates 64.95.72.241 as permitted sender)
To: Kris Craig <kris.craig@gmail.com>, Matthew Weier O'Phinney
	<weierophinney@php.net>
CC: "internals@lists.php.net" <internals@lists.php.net>
Date: Fri, 13 Apr 2012 15:12:10 -0400
Thread-Topic: [PHP-DEV] [RFC] New .phpp File Type for Pure-Code PHP Scripts
Thread-Index: Ac0ZpcAbUlNRfIhpQGCqAARGKRhQbgAATGUA
Message-ID: <A633CF2D7C7BED41B41F1E64F25507B806A5CDD8B5@MAILR001.mail.lan>
References: <CAKOpQSwYe+tZ3JfLFWaOHCnBpUyy9yoA61=qLzbnnOKTL0mQdQ@mail.gmail.com>
 <CAGa2bXa554p45tbNFvtHQJiYTXaa0eD6r+qnExDVk+6e8PRvMw@mail.gmail.com>
 <4F876943.8030105@gmail.com>
 <CAKOpQSzAZauE9HYK3x-5UbxAstkdkc-HkfZRa+E+i=DNxQwkBA@mail.gmail.com>
 <4F877777.8050806@gmail.com>
 <CAKOpQSyC6Zs=3-AQ8=L-aufTP03j0yhnRiu3n6pNP7YSpW_KLg@mail.gmail.com>
 <4F8782CC.8030205@gmail.com>
 <CAKOpQSzKo9ZX1voYppTRihkfkpfCywMLLv_DF8XWGxcOV1Su8Q@mail.gmail.com>
 <CAGsnKxaR8vHHeZrpDhf4WVBKqDwMXrAf=b=3r06oJZpP4K3sPg@mail.gmail.com>
 <CAKOpQSyVu3ddZubCeo4BpZTWFXf55_yYNbrhDqTJkDjPoX6xVw@mail.gmail.com>
 <CAGsnKxatwB-T5ExGjq9z0FyjhRB0DKVRigu=opqXbjoyUAcwRA@mail.gmail.com>
 <CAKOpQSy3BVpY-UNSvVkQSoPBV=ZKdiJ0nOC14ou3YRdJM5XmnQ@mail.gmail.com>
 <13.6A.35770.615388F4@pb1.pair.com>
 <CAKOpQSznwqVb_iVoKf76dswWwL4OGa4Zj8C+iYj+W4RUrMErTg@mail.gmail.com>
In-Reply-To: <CAKOpQSznwqVb_iVoKf76dswWwL4OGa4Zj8C+iYj+W4RUrMErTg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: RE: [PHP-DEV] [RFC] New .phpp File Type for Pure-Code PHP Scripts
From: johncrenshaw@priacta.com (John Crenshaw)

> >
> > On top of this, there's an argument that you're not addressing: most=20
> > template engines in PHP either directly consume PHP template files...
> > or "compile" templates into... PHP template files. As such, sooner or=20
> > later, you'll have a class that includes a PHP template file, and=20
> > 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 entang=
led,
> the very notion of a pure PHP stack is just incompatible.  So your best b=
et
> 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 wors=
e, 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 communi=
ty. This effectively attempts to split PHP into two languages. Current PHP =
isn't really compatible with the proposed ".phpp" version of PHP, in the se=
nse that you can't safely use both in the same code base. Unfortunately thi=
s will not be clear to anybody at first, which will lead to mass proliferat=
ion of .phpp libraries which are like poison to any unsuspecting PHP user f=
oolish 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