On Mon, 25 Mar 2019 at 20:42, Andrey Andreev <n...@devilix.net> wrote:
> Hi, > > On Mon, Mar 25, 2019 at 8:02 PM G. P. B. <george.bany...@gmail.com> wrote: > > > > On Mon, 25 Mar 2019 at 16:38, Andrey Andreev <n...@devilix.net> wrote: > >> > >> OK, so why not flip it and make it always available instead? I'm aware > >> of the potential XML conflict, but I've personally never seen it, so > >> to me that looks like the lesser evil compared to a massive BC break. > >> > >> Cheers, > >> Andrey. > > > > > > Technically this is already the case, the default in the engine is to > enable PHP's short open tags, however both INI config templates provided > > with PHP (php.ini-developement and php.ini-production) disable PHP's > short open tags. > > So if PHP's short open tags are to be considered "full class" open tags > this should be represented in the INI templates. But I won't be the > > one pushing for this change. > > > > We're talking about removal of the INI setting ... Aside of saying you > wouldn't be personally pushing for what I suggested, I don't get the > point of what you wrote. > > Cheers, > Andrey. > The point of what I wrote was to clarify what is the default value in-engine of short open tags. Also updated the RFC with the fact that using PHP's short open tags may leaks source code if used when those aren't not enabled. Best regards George P. Banyard
