Tom, As I've said before I don't think new keywords are the answer. They will just pollute the language even further.
I also don't think an ini setting is a bad thing either. It is often used in PHP as a way to transition from way of doing things to another. First you introduce it with it being off by default, then on by default, then deprecate the old behavior. It's quite normal in PHP's history. In another email someone mentioned doing two rfcs. In both cases are we talking about removing <?php ? Because it's become somewhat confusing to keep track of what is being talked about. If that is the case, continue reading. I would prefer the starting <?php tag be optional rather than removed. Just explicitly forbid the ending ?> tag and treat text before the opening <?php tag differently. Perhaps ignore it (rather than print) or throw an error. That is at least how I would prefer the "code" mode as most non-template files only start with <?php. It allows for backwards compatibility. If you must add keywords it should be something like require_template NOT require_code/require_file. Templates are the exception, not the norm. Luke Scott On Apr 8, 2012, at 9:32 AM, Tom Boutell <t...@punkave.com> wrote: > I have written an RFC proposing backwards-compatible support for > source files without an opening <?php tag: > > https://wiki.php.net/rfc/source_files_without_opening_tag > > This RFC is not yet listed at https://wiki.php.net/rfc. I am not sure > what the requirements are to get it added to the "Under Discussion" > session and get the ball rolling formally. Please enlighten and I'll > do whatever is required. > > Thanks! > > -- > 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 > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
