Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59396
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain charliesomerville.com from 209.85.160.42 cause and error)
Date: Sat, 7 Apr 2012 23:30:14 +1000
To: Tom Boutell <tom@punkave.com>
Cc: PHP Internals <internals@lists.php.net>
Message-ID: <7150E78F35F64C42B171FF37A7EAF9B0@charliesomerville.com>
In-Reply-To: <CAORXhGLk8=bJ2TEo0OCzQCacjtGG=ZWYNuXf8Uu8oMNEm2WQ1A@mail.gmail.com>
References: <CAORXhGLk8=bJ2TEo0OCzQCacjtGG=ZWYNuXf8Uu8oMNEm2WQ1A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="4f804166_3d1b58ba_6dd6"
Subject: Re: [PHP-DEV] PHP class files without <?php at the top
From: charlie@charliesomerville.com (Charlie Somerville)

--4f804166_3d1b58ba_6dd6
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I'm +1 on this.

<?php isn't a *huge* issue, but it is a bit of an annoyance. 'phpc' would help fix that up IMO. 


On Saturday, 7 April 2012 at 11:26 PM, Tom Boutell wrote:

> Now that the flamewar has died down a little I'd like to try to have a
> civil discussion about this idea - *without* my admittedly
> inflammatory suggestion to kill <?php altogether.
> 
> So here is what I am seriously suggesting:
> 
> * The default behavior doesn't change. The parser starts out in HTML mode.
> 
> * 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 ?>.
> 
> * If a require/include statement sees a .phpc file extension, the
> parser starts out in PHP mode.
> 
> * If mod_php and FPM are able to see the path (I'm honestly not sure
> if they can or not), they look for .phpc as their indication to start
> out in PHP mode. If that's not possible then new options are defined
> to allow Apache to be configured to tell mod_php and/or FPM to do the
> right thing based on mime types etc.
> 
> This way .php continues to behave exactly as it does today, and can
> interoperate smoothly with code that uses .phpc. .phpc can require
> .php and vice versa. They are friends.
> 
> Thoughts?
> 
> -- 
> Tom Boutell
> P'unk Avenue
> 215 755 1330
> punkave.com (http://punkave.com)
> window.punkave.com (http://window.punkave.com)
> 
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
> 
> 



--4f804166_3d1b58ba_6dd6--