On Wed, Apr 11, 2012 at 1:48 PM, Chris Stockton <chrisstockto...@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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
