Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59434
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
References: <CAORXhGLk8=bJ2TEo0OCzQCacjtGG=ZWYNuXf8Uu8oMNEm2WQ1A@mail.gmail.com>
In-Reply-To: <CAORXhGLk8=bJ2TEo0OCzQCacjtGG=ZWYNuXf8Uu8oMNEm2WQ1A@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii
Message-ID: <EA16B435-6E10-4AA9-BEFC-A0A03CAE5F15@schlueters.de>
Cc: PHP Internals <internals@lists.php.net>
Date: Sat, 7 Apr 2012 20:12:44 +0200
To: Tom Boutell <tom@punkave.com>
Subject: Re: [PHP-DEV] PHP class files without <?php at the top
From: johannes@schlueters.de (=?utf-8?Q?Johannes_Schl=C3=BCter?=)



On Apr 7, 2012, at 15:26, Tom Boutell <tom@punkave.com> wrote:
> * If the CLI sees a .phpc file extension, the parser starts out in PHP
> mode (no opening <?php is required). It is still possible to shift
> into HTML mode after that with ?>.
>=20
> * If a require/include statement sees a .phpc file extension, the
> parser starts out in PHP mode.

I don't think such magic is good. It will rather confuse people. Back when I=
 thought about this my best idea was a flag to include/require which at some=
 point will emit a notice if not set and where in the long run the default c=
hanges. But I dropped the idea. Reasons include the fact that the whole envi=
ronment is being forced to change (IDEs, code checkers, ...) and well most p=
eople not only have to type the opening tag but also some file header (licen=
se, phpdoc, ...) which makes the benefit smaller. And then there's another t=
hought: The <?php makes it trivial to identify PHP code as such, especially w=
hen discussing snippets or such.

My conclusion is that I can see reasons to change this, while in my opinion i=
t's not worth it.

johannes