Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59745
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain punkave.com designates 209.85.160.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CALKFbxvfNPdibvPJvWWLo+T8K9F0SLS64GNfvwHLN4TNQjh4PA@mail.gmail.com>
References: <CAORXhGK47pRN8uUTENqSbddQoCP8VopomPhJW7N2pN6ZU8vNPQ@mail.gmail.com>
	<CALKFbxvfNPdibvPJvWWLo+T8K9F0SLS64GNfvwHLN4TNQjh4PA@mail.gmail.com>
Date: Wed, 11 Apr 2012 14:14:09 -0400
Message-ID: <CAORXhGJ5GULr3J+XxUthBr0pF93=uFQSKw-ftKSs=cY77ZYi8Q@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] UPDATED RFC version 1.1: source files without opening
 <?php tag
From: tom@punkave.com (Tom Boutell)

On Wed, Apr 11, 2012 at 1:48 PM, Chris Stockton
<chrisstocktonaz@gmail.com> wrote:
> I have read the RFC and I although from what I gather it seems that
> .phpp is a recommendation and not a requirement, but I want to make
> absolutely sure.


That is correct, it is not a requirement. However if you know of any
reason why .phpp would be a bad choice of file extension for PHP
source files without <?php and ?> in them, now would be a good time to
share that input.

> My only other issue is that we are not really following the guidelines
> for reserved constants, since "include" is not part of a "include"
> extension and a actual language construct it feels like it should live
> inside the reserved PHP_* constants. There may be projects that make
> use of "INCLUDE_ONCE" as a constant or maybe not, regardless I think
> it should follow the documented naming guidelines to be safe.

I wasn't aware of those guidelines. This makes sense to me.
PHP_INCLUDE_ONCE, then?

-- 
Tom Boutell
P'unk Avenue
215 755 1330
punkave.com
window.punkave.com