From: Tom Boutell [mailto:t...@punkave.com] > John, please take a look at the RFC: > > https://wiki.php.net/rfc/source_files_without_opening_tag > > I am not proposing any backwards-incompatible changes that would affect > existing code. Code that isn't interested need not ever take advantage of the > feature and can interoperate with code that does. I realize there is > confusion about this because of a separate and unrelated RFC to actually > eliminate <?php. > > I agree that the security argument is bogus, but it was never one of my > reasons for this proposal. >
Yeah, the discussion isn't always focused. I was responding to some arguments that are mostly separate from what is specifically proposed in your RFC. About the RFC: 1. Passing two parameters to a keyword feels super awkward. I think it's fair to require this to be used more like a function. 2. IMO the selected name (require_path) is confusing. There are still some ecosystem issues, and interoperability is somewhat reduced in the sense that all 3rd party code would have to be checked for the <?php, but I *think* I can live with that. I still don't see a strong reason for eliminating the opening tag, but in my mind the substance of this proposal is really more about opening the door to more flexible inclusion in the future, and I can get behind that. John Crenshaw Priacta, Inc. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
