Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59555
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain punkave.com designates 209.85.217.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F834D82.4030601@developersdesk.com>
References: <CAORXhGJwmbjw3Zze3+-oFA2Mb_Z-2owVESraNMMs57RzjRRMbA@mail.gmail.com>
	<-5877502932356715576@unknownmsgid>
	<CAORXhGLPdAie6UFq+daJhUmDUqp7RaFFLa596XdzdtuCddf0Jw@mail.gmail.com>
	<-3647345967307864634@unknownmsgid>
	<CAORXhGKjg_L11dFGNHNfNygDH018=ZhytAy1vH+Ei8QHfry=cA@mail.gmail.com>
	<CAORXhG+K3XML-47+FDYdL5D717wDX7c59Pz8KgqjcP16+Ad12w@mail.gmail.com>
	<4F831FAE.2030208@ralphschindler.com>
	<4775322189440202047@unknownmsgid>
	<CAORXhGJSG6CJD5EAt_uZ7RjfjM345nfrVQz8t2ep4e3WhCeKMQ@mail.gmail.com>
	<4F833682.2000301@ralphschindler.com>
	<CAGa2bXYjJsfo6os_P1OvQ7jfmxeYUkZ+QK5r94nwNUsba-iWLA@mail.gmail.com>
	<4F833AB0.2060306@sugarcrm.com>
	<CAGa2bXa4U3ar2REYahyt_0pJH=mjNjvHUhmHpxL+Qkdy3tUZFQ@mail.gmail.com>
	<4F8340E6.90005@sugarcrm.com>
	<CAGa2bXY0fXX_SSYtsdw2xVqE=V6t+8B_-daPo5YrRd6E_HuPfQ@mail.gmail.com>
	<CAKOpQSz2oTBCdgxsCBoeDUJaG=hA9Hx-S6jMJ7rtqcn1hbEnAw@mail.gmail.com>
	<4F834D82.4030601@developersdesk.com>
Date: Mon, 9 Apr 2012 17:03:04 -0400
Message-ID: <CAORXhGKQAMgpyLpTtCTCSNfELf73GXaFtzEtymjLCfRjEW5WWg@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] RFC: source files without opening tag
From: tom@punkave.com (Tom Boutell)

As others explained before the RFC was drafted, file extensions should
not be directly respected by PHP because environments differ too much.
Instead a convention, NOT enforced at the code level, would be
published and encouraged: .phpc for files that start out in PHP mode,
and .php for files that start out in HTML mode. PHP would NOT enforce
this, it would just be an encouraged practice in the writing of
autoloaders and so on. (Note that autoloaders are already concerned
with file extensions. They have to be in order to transform a class
name into a filename.)

The RFC does not call for putting an end to the traditional use of PHP
for templates at all, that is still the default behavior when parsing
PHP. There is an entirely separate RFC that calls for that, but that's
another thread.

On Mon, Apr 9, 2012 at 4:58 PM, Rick WIdmer <vchkpw@developersdesk.com> wro=
te:
> On 4/9/2012 2:41 PM, Kris Craig wrote:
>>>
>>>
>> Honestly, I would suggest just getting rid of "Option 1" altogether. =A0=
It
>> would end up over-complicating this to such a degree that any usefulness
>> it
>> might serve would be considerably diminished.
>>
>> As for embedded HTML, if you allow the ?> =A0tag in these .phpp files, t=
hen
>> that pretty much negates the entire purpose of having them to begin with=
.
>> Essentially, you'd just be changing it so that, instead of defaulting to
>> "?>" when no tag is present, it defaults to"<?php". =A0I just don't see =
any
>> value in that as a developer.
>>
>> A developer should *not* be including in a .phpp file classes that conta=
in
>> HTML within the ?> =A0tag, period. =A0If they need to include something =
that
>> has
>> that, they should do it in a regular .php file. =A0An "HTML-less" PHP fi=
le
>> needs to be exactly that; no direct HTML allowed. =A0Otherwise, the RFC =
is
>> completely and utterly pointless IMHO.
>>
>>
>> I think this would be awesome for PHP 6, but I'll have to vote against i=
t
>> if you settle on using "Option 1" and/or allow ?> =A0content to be
>> embedded/included in .phpp files. =A0If we differentiate based solely on=
 the
>> file extension and keep ?> =A0tags out of it, then I'll definitely suppo=
rt
>> it!
>
>
>
>
> Please forget about file extensions. =A0PHP should not consider file
> extensions. =A0The only reason .php files are executed by PHP is because =
the
> web browser is configured to pass that extension to PHP rather than handl=
e
> it internally.
>
>
> I sincerely hope that any suggestion to eliminate the ability to use PHP =
as
> a template engine will be met with a veto by the core developers, or mayb=
e
> even another suggestion by the trademark owner of PHP that he will not al=
low
> the PHP name to be used on such a language.
>
>
>
>
>
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>



--=20
Tom Boutell
P'unk Avenue
215 755 1330
punkave.com
window.punkave.com