On Sun, Feb 9, 2014 at 11:35 PM, Yasuo Ohgaki <[email protected]> wrote:
> Hi all,
>
> "Optional PHP tags by php.ini and CLI options" RFC has been discussed very
> long time.
>
> https://wiki.php.net/rfc/nophptags
>
> I would like to know is there anyone who would like not to have
> this. I think it's good counter measure for LFI, but you might have
> different perspective.
>
> If it is possible, I would like to address as much as opinions possible
> before voting.
>
> Are there anyone who think we should have this?
> What is the reason?
>
> Thank you
>
> --
> Yasuo Ohgaki
> [email protected]
>
Though I realize I'm in the minority here, I've always supported the idea
of doing something like this. From an MVC standpoint, it would be nice to
be able to include script-only files. These scripts would not be able to
include template mode scripts, either.
The main problem is, as others have stated, the fact that it'll be very
prone to human error. If someone includes a script-only file as template
mode, they'd be dumping the entire source for all the world to see. The
only way around that-- as far as I can figure, at least-- would be to throw
an exception when including a template mode file that doesn't contain a PHP
open tag. The problem with that, unfortunately, is that it would almost
certainly cause BC breakage. That may or may not be acceptable for a major
increment like PHP 6, but certainly not for the 5.x branch.
There's also the usefulness question. While I agree that it's definitely
not a "must have" feature, I would venture to say it does qualify as a
"would be nice" feature. Whether or not that merits implementation would
be a matter for debate. It might be useful to include this in the next
poll we do and see what the larger dev community thinks about this, as it's
something we've debated off-and-on for years now.
--Kris