Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104768
MIME-Version: 1.0
References: <CAFPFaMLC6beM1Tmud-fJQ-2inUhAPXo8WAY1mvEO26jdcNos7g@mail.gmail.com>
 <ae023782-a51f-a93d-d4a1-626b02f9ea65@gmail.com> <CALGLHq0vV-0Jm3HBT0wM8dFvE5VagHcTu+2TOUphdaEeO0HdfA@mail.gmail.com>
In-Reply-To: <CALGLHq0vV-0Jm3HBT0wM8dFvE5VagHcTu+2TOUphdaEeO0HdfA@mail.gmail.com>
Date: Sat, 16 Mar 2019 04:19:04 +0100
Message-ID: <CAAfnsFVUyBFAzNgfGB6PWvKFhOmm5rTZTOpjyY5CFqS7HRA1Dw@mail.gmail.com>
To: Morgan Breden <morganbreden@gmail.com>
Cc: xellisx@gmail.com, Internals <internals@lists.php.net>, 
	"G. P. B." <george.banyard@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Deprecate short_open_tag ini directive? PHP internals <internals@lists.php.net>
From: peterkokot@gmail.com (Peter Kokot)

Hello,
On Sat, 16 Mar 2019 at 03:57, Morgan Breden <morganbreden@gmail.com> wrote:
>
> >If you want to go further, dropping the PHP tag altogether would be nice,
> since it would prevent context switching between PHP/HTML/JS/whatever.
> >That would force Wordpress to update their whole
> code base. >:{)>
>
> I wholeheartedly support this initiative but I do not see it going through
> without a lot of resistance. Using PHP itself as a templating engine is
> part of what makes it so "newbie friendly".

I think using PHP tags for templates and option to write code without
opening tag might go through also. After all, text files are simple.

Something on this was already being done and probably also discussed:
https://wiki.php.net/rfc/nophptags

On the other hand, shebangs will still be present in CLI scripts. For example:
#!/usr/bin/env php

-- 
Peter Kokot