Re: UPDATED RFC version 1.1: source files without opening <?php tag

From: Date: Wed, 11 Apr 2012 17:48:13 +0000
Subject: Re: UPDATED RFC version 1.1: source files without opening <?php tag
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-59741@lists.php.net to get a copy of this message
Hello, On Tue, Apr 10, 2012 at 4:53 PM, Tom Boutell <tom@punkave.com> wrote: > Please see: > > https://wiki.php.net/rfc/source_files_without_opening_tag > > After following the discussion I have updated the RFC with the > following major changes: > > * Forbade the use of ?> entirely in "pure PHP" files (without > restricting it at all in other PHP files) > > * Replaced my original new require_path keyword with a second, > optional parameter to the standard include/require family of keywords > > * Replaced an array of options with a bitwise OR of options > > * Changed the proposed filename extension from .phpc (which apparently > is in use somewhere, maybe?) to .phpp ("php pure") > 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. 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. -Chris

« previous php.internals (#59741) next »