Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59529
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain punkave.com designates 209.85.161.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <A633CF2D7C7BED41B41F1E64F25507B806A5CDD5E2@MAILR001.mail.lan>
References: <CAORXhGLk8=bJ2TEo0OCzQCacjtGG=ZWYNuXf8Uu8oMNEm2WQ1A@mail.gmail.com>
	<CAGa2bXYP0kNA5PyvmdjoHZO91t8AojG9FjUe4nbCHhGjn2=MPg@mail.gmail.com>
	<4F80C739.2060404@gmail.com>
	<CAGa2bXZSgV3bRPGMt6Esw16v3ErVMLVQy1fb8cZxdc=OokpXKg@mail.gmail.com>
	<CAL0xaBEpjhwTMFknx9nPYXqFGOqM9f2xRiBhcdb8NtPCsVL6sg@mail.gmail.com>
	<CAGa2bXaEZ1rkkQ1MTCQ8=eet9P9oAWXz-cPMe5wRhHfFJE8N8Q@mail.gmail.com>
	<CAORXhG+eg8kS9Xqyt4WdH0H5C6H5P09Uc9+U5LA0RWrs5iR5ow@mail.gmail.com>
	<CAGa2bXbtJ3ksL_iaeZ0+DGU5veKegNRS0LY1s=zrZVNwLLvt7Q@mail.gmail.com>
	<CAL0xaBGGFRqq9tkc33daKoqTNHsLNmgadkUEjJtrGGJsWfK+YQ@mail.gmail.com>
	<CAGa2bXZa=DS0YS2aL5nobGZif23qbCcAMQMaagdG2-HFffCiVg@mail.gmail.com>
	<A633CF2D7C7BED41B41F1E64F25507B806A5CDD5C0@MAILR001.mail.lan>
	<CAORXhGLa+P9_oy-hQZt6wjR5Fy1SjF9Y9ZweBdNjybkJaSc=RQ@mail.gmail.com>
	<A633CF2D7C7BED41B41F1E64F25507B806A5CDD5D7@MAILR001.mail.lan>
	<CAORXhG+b+SUYR45ppDLyq4e3RGnYNq6Wdo9OTi2QFXKH0jdzwg@mail.gmail.com>
	<A633CF2D7C7BED41B41F1E64F25507B806A5CDD5E2@MAILR001.mail.lan>
Date: Mon, 9 Apr 2012 14:45:08 -0400
Message-ID: <CAORXhGKepSqDf=ncTV8fR8VhbozQNoAUCc7+7PZhiM96u99ZNA@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] PHP class files without <?php at the top
From: tom@punkave.com (Tom Boutell)

Such code would have the .phpc extension, so it wouldn't get loaded at
all by most autoloaders that aren't prepared for it I imagine.

This feature would certainly make the most sense as part of a new
version of PHP that introduces other new functionality. "I'm going to
use feature X in this code, which doesn't exist in version Y anyway,
so I may as well take advantage of not having to type <?php anymore as
well."

On Mon, Apr 9, 2012 at 1:33 PM, John Crenshaw <johncrenshaw@priacta.com> wr=
ote:
> From: Tom Boutell [mailto:tom@punkave.com]
>>
>> On Mon, Apr 9, 2012 at 12:43 PM, John Crenshaw <johncrenshaw@priacta.com=
> wrote:
>> > interoperability is somewhat reduced in the sense that all 3rd party
>> > code would have to be checked for the <?php
>>
>> I'm not sure what you mean by this part exactly?
>
> Suppose a code library is written and the author writes it without the <?=
php at the head of each file. Using that library in a project that opted to=
 keep the <?php requires adding this to the head of each file, or else ensu=
ring that the library is always included with the code parameter set (which=
 could get really messy with autoloaders.) Additionally (assuming that you =
modified the code files) updating the library in the future gets really mes=
sy. It's not the end of the world, but it's frustrating. I'd like to believ=
e that most library authors will be smart enough to always include the <?ph=
p for compatibility purposes, but I'm sure some won't.
>
> John Crenshaw
> Priacta, Inc.



--=20
Tom Boutell
P'unk Avenue
215 755 1330
punkave.com
window.punkave.com