# [RFC] [VOTE] Deprecate PHP's short open tags, again

- Thread: https://externals.io/message/106384
- Original archive: https://news-web.php.net/php.internals/106384
- Started by G. P. B. on 2019-08-06T11:34:22+00:00
- Messages: 83
- RFC: PHP RFC: Deprecate short open tags, again (Declined) — https://externals.io/rfc/deprecate_php_short_tags_v2.md
- Page 1 of 4: messages 1 to 25 (25 per page, add `?page=N` to the URL)
- Next page: https://externals.io/message/106384.md?page=2
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · RFCs at https://externals.io/rfc.md · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #106384 — G. P. B. — 2019-08-06T11:34:22+00:00

URL: https://externals.io/message/106384#106384

The voting for the "Deprecate short open tags, again" [1] RFC has begun.
It is expected to last two (2) weeks until 2019-08-20.

A counter argument to this RFC is available at
https://wiki.php.net/rfc/counterargument/deprecate_php_short_tags

Best regards

George P. Banyard

[1] https://wiki.php.net/rfc/deprecate_php_short_tags_v2

---

## #106391 — Chase Peeler — 2019-08-06T16:59:13+00:00

URL: https://externals.io/message/106384#106391 · In reply to: #106384

I'm not a voter, but, I have a question. If this fails, does that mean the
original RFC that passed is still in effect?

If I did have a vote, I would be against this RFC for the reasons laid out
by Zeev in the counter argument. However, I feel the negative impacts of
possible code leaks that will be caused by the original RFC are even worse.
If I did have a vote, I might feel forced to vote for this. At least with
this RFC we wouldn't really see any of the other negative impacts until PHP
9, given us time to revisit and possibly reverse that part of this RFC.



> The voting for the "Deprecate short open tags, again" [1] RFC has begun.
> It is expected to last two (2) weeks until 2019-08-20.
>
> A counter argument to this RFC is available at
> https://wiki.php.net/rfc/counterargument/deprecate_php_short_tags
>
> Best regards
>
> George P. Banyard
>
> [1] https://wiki.php.net/rfc/deprecate_php_short_tags_v2
>


-- 
Chase Peeler
chasepeeler@gmail.com

---

## #106392 — Rowan Collins — 2019-08-06T17:11:54+00:00

URL: https://externals.io/message/106384#106392 · In reply to: #106391

> I'm not a voter, but, I have a question. If this fails, does that mean the
> original RFC that passed is still in effect?
>


Yes, this is really ambiguous, and risks the situation being even more
confusing than it was before.

The "No" column on this RFC already includes people who voted "Yes" on the
previous version; is this an indication that they have changed their mind
about removing short tags, or that they prefer the original proposal?

I think we urgently need to clarify this, and may need to reset the vote
with one or more clearer questions.

Regards,
-- 
Rowan Collins
[IMSoP]

---

## #106393 — G. P. B. — 2019-08-06T17:19:39+00:00

URL: https://externals.io/message/106384#106393 · In reply to: #106392

> 
>
> > […]
> the
> > […]
>
>
> Yes, this is really ambiguous, and risks the situation being even more
> confusing than it was before.
>
> The "No" column on this RFC already includes people who voted "Yes" on the
> previous version; is this an indication that they have changed their mind
> about removing short tags, or that they prefer the original proposal?
>
> I think we urgently need to clarify this, and may need to reset the vote
> with one or more clearer questions.
>
> Regards,
> --
> Rowan Collins
> [IMSoP]


This RFC supersedes the previous one as stated in the the RFC itself : "
This RFC supersedes the previous one and proposes a different deprecation
approach." meaning that the previous one is void.
I don't know why this is ambiguous and needs to be said once again.

Best regards

George P. Banyard

---

## #106394 — Peter Kokot — 2019-08-06T17:23:06+00:00

URL: https://externals.io/message/106384#106394 · In reply to: #106393

Hello,


>
> 
>
> > […]
>
>
> This RFC supersedes the previous one as stated in the the RFC itself : "
> This RFC supersedes the previous one and proposes a different deprecation
> approach." meaning that the previous one is void.
> I don't know why this is ambiguous and needs to be said once again.
>
> Best regards
>
> George P. Banyard


Thank you for clarification. From what I understand it is the case
where "no" means a status quo and no agreements has been reached on
the original RFC. Since the original RFC has been vetoed and so much
energy was invested from Zeev and some others commentators then I
guess the RFCs fail and we will have two types of opening tags in PHP
for ever. Otherwise, as described, yes.



-- 
Peter Kokot

---

## #106395 — Chase Peeler — 2019-08-06T17:25:17+00:00

URL: https://externals.io/message/106384#106395 · In reply to: #106393

>
>
>
> On Tue, 6 Aug 2019 at 19:12, Rowan Collins <rowan.collins@gmail.com>
> wrote:
>
> > […]
>
>
> This RFC supersedes the previous one as stated in the the RFC itself : "
> This RFC supersedes the previous one and proposes a different deprecation
> approach." meaning that the previous one is void.
> I don't know why this is ambiguous and needs to be said once again.
>
> Just to clarify - the existence of this RFC effectively means the original
never existed.


> Best regards
>
> George P. Banyard
>


-- 
Chase Peeler
chasepeeler@gmail.com

---

## #106396 — G. P. B. — 2019-08-06T17:27:49+00:00

URL: https://externals.io/message/106384#106396 · In reply to: #106395

>
>
> 
>
> > […]
> original never existed.
>
>
> > […]
>
>
> --
> Chase Peeler
> chasepeeler@gmail.com
>

In a sense yes, however this RFC is a vote on the implementation which
would have landed with the previous one but was not the one voted.
So you can disregard the result of the previous one not the controversial
discussion it generated after the vote was accepted.

Hope this clarifies everything.

Best regards

George P. Banyard

---

## #106397 — Nikita Popov — 2019-08-06T18:46:15+00:00

URL: https://externals.io/message/106384#106397 · In reply to: #106384

> The voting for the "Deprecate short open tags, again" [1] RFC has begun.
> It is expected to last two (2) weeks until 2019-08-20.
>
> A counter argument to this RFC is available at
> https://wiki.php.net/rfc/counterargument/deprecate_php_short_tags
>
> Best regards
>
> George P. Banyard
>
> [1] https://wiki.php.net/rfc/deprecate_php_short_tags_v2
>

Side-note: Even if this RFC fails, we should probably still make it an
error to use <? without short_tags being **explicitly** enabled, so that we
may flip the default to off at some later point in time. The current
default being "on" despite their use being discouraged is half the trouble.

Nikita

---

## #106398 — Zeev Suraski — 2019-08-06T19:16:12+00:00

URL: https://externals.io/message/106384#106398 · In reply to: #106397

> 
> 
> > […]
> 
> Side-note: Even if this RFC fails, we should probably still make it an
> error to use <? without short_tags being **explicitly** enabled, so that we
> may flip the default to off at some later point in time. The current
> default being "on" despite their use being discouraged is half the trouble.
> 

That’s a good idea.  I was genuinely surprised to learn that wasn’t already the case, although the actual impact of that is quite limited given the fact that virtually all common deployments come preconfigured with short tags set to off.

Zeev

---

## #106400 — Claude Pache — 2019-08-06T21:55:13+00:00

URL: https://externals.io/message/106384#106400 · In reply to: #106397

> Le 6 août 2019 à 20:46, Nikita Popov <nikita.ppv@gmail.com> a écrit :
> 
> 
> 
> > […]
> 
> Side-note: Even if this RFC fails, we should probably still make it an
> error to use <? without short_tags being **explicitly** enabled, so that we
> may flip the default to off at some later point in time. The current
> default being "on" despite their use being discouraged is half the trouble.
> 
> Nikita


That would mean in particular that XML documents could no longer be preprocessed by PHP without boilerplate around its `<?xml ?>` declaration. I doubt that this is a more acceptable breaking change than deprecating short_tags.

—Claude

---

## #106401 — Walter Parker — 2019-08-06T22:45:17+00:00

URL: https://externals.io/message/106384#106401 · In reply to: #106400

>
>
> > […]
> wrote:
> > […]
> we
> > […]
> trouble.
> > […]
>
>
> That would mean in particular that XML documents could no longer be
> preprocessed by PHP without boilerplate around its `<?xml ?>` declaration.
> I doubt that this is a more acceptable breaking change than deprecating
> short_tags.
>
> —Claude
> --
> 
> 
>
> Why would you want to use PHP's preprocessor for XML?
Why not use the right tool for the job? Such as an XML processor that could
also do schema validation? PHP has XML processing packages. It has been a
while since I did XML processing, but I don't remember the packages being
all that difficult to use. Is this a mixing data and code into the same
file problem? Like HTML files that have PHP embedded directly in the file?
Or this about stuffing PHP inside of XML documents?


Walter

-- 
The greatest dangers to liberty lurk in insidious encroachment by men of
zeal, well-meaning but without understanding.   -- Justice Louis D. Brandeis

---

## #106403 — Andrey Andreev — 2019-08-07T07:28:00+00:00

URL: https://externals.io/message/106384#106403 · In reply to: #106393

Hi,


>
> This RFC supersedes the previous one as stated in the the RFC itself : "
> This RFC supersedes the previous one and proposes a different deprecation
> approach." meaning that the previous one is void.
> I don't know why this is ambiguous and needs to be said once again.
>

As far as I know, there's been no vote to cancel the previously
accepted RFC, so ... even though I didn't like the outcome of it, I
don't understand how it is just made void now. It's pretty easy to
understand the ambiguity.

I won't be voting on this one due to all of this.

Cheers,
Andrey.

---

## #106404 — Nikita Popov — 2019-08-07T08:11:20+00:00

URL: https://externals.io/message/106384#106404 · In reply to: #106400

>
>
> > […]
> wrote:
> > […]
> we
> > […]
> trouble.
> > […]
>
>
> That would mean in particular that XML documents could no longer be
> preprocessed by PHP without boilerplate around its `<?xml ?>` declaration.
> I doubt that this is a more acceptable breaking change than deprecating
> short_tags.


To clarify: What I had in mind is that use of <? results in an error if and
only if short_tags is left at its default value (of On). If short_tags is
explicitly Off or explicitly On, everything works as usual. Embedding <?xml
?> in PHP code requires an explicit short_tags=Off right now, so the
situation there shouldn't change, unless I'm missing something.

The only motivation here is to allow us to change the default to
short_tags=Off at some point in the future (say PHP 9), after enough time
has passed where short_tags cannot be used by default, without explicitly
being enabled. We can't just flip the default right now due to the usual
code leaking concerns.

Regards,
Nikita

---

## #106405 — Peter Kokot — 2019-08-07T08:44:57+00:00

URL: https://externals.io/message/106384#106405 · In reply to: #106403

Hello,


>
> Hi,
>
> 
> > […]
>
> As far as I know, there's been no vote to cancel the previously
> accepted RFC, so ... even though I didn't like the outcome of it, I
> don't understand how it is just made void now. It's pretty easy to
> understand the ambiguity.
>
> I won't be voting on this one due to all of this.
>
> Cheers,
> Andrey.
>
> --
> 
> 
>

Yes, last time I was asking this, there was a clarification that
certain people from the group internals can veto particular RFC. So, I
think that this is the case here.

-- 
Peter Kokot

---

## #106406 — Christoph M. Becker — 2019-08-07T09:39:35+00:00

URL: https://externals.io/message/106384#106406 · In reply to: #106405

> 
>
> > […]
>
> Yes, last time I was asking this, there was a clarification that
> certain people from the group internals can veto particular RFC. So, I
> think that this is the case here.

I'm not aware of *any* veto rights regarding RFCs.  As I understand it,
this RFC has been put to vote again, because the first version had some
problematic details, and by courtesy to cater to the clamor raised after
the voting had finished.

Thanks,
Christoph

---

## #106407 — Zeev Suraski — 2019-08-07T10:06:48+00:00

URL: https://externals.io/message/106384#106407 · In reply to: #106406

As I understand it, this RFC has been put to vote again, because the first version had some problematic details, and by courtesy to cater to the clamor raised after
the voting had finished.

That is correct.  There was an inconsistency with the Voting RFC in the voting options, and the RFC (as it passed) also had catastrophic implications for upgrades - so it could not be implemented as it was written.

Zeev

---

## #106408 — Rowan Collins — 2019-08-07T13:12:07+00:00

URL: https://externals.io/message/106384#106408 · In reply to: #106404

> To clarify: What I had in mind is that use of <? results in an error if and
> only if short_tags is left at its default value (of On). If short_tags is
> explicitly Off or explicitly On, everything works as usual. Embedding <?xml
> ?> in PHP code requires an explicit short_tags=Off right now, so the
> situation there shouldn't change, unless I'm missing something.


Since it would behave differently, it wouldn't make sense to say that it 
defaulted to "On", but that actually leads to an interesting feature: 
add an "error" mode to that setting. So the options would be:

- error: any use of "<?" other than "<?php" and "<?=" would raise an 
error; compile-time default
- off: "<?" is ignored and passed through to output; ini default shipped 
by most packages
- on: "<?" is equivalent to "<?php"; no longer any kind of default

We could either leave the recommended ini setting in the official 
distribution as "off" (more compatible) or set it to "error" (to make 
mistakes safer and easier to spot).

Regards.

-- 
Rowan Collins
[IMSoP]

---

## #106410 — Dan Ackroyd — 2019-08-07T13:55:55+00:00

URL: https://externals.io/message/106384#106410 · In reply to: #106405

>
> Yes, last time I was asking this, there was a clarification that
> certain people from the group internals can veto particular RFC.

Please could you point to where this alleged rule has ever been
written down or agreed to?

Although certain people may have claimed this is a rule, it's never
been agreed afaik.

I think when we adopt a Code of Conduct one of the things we need to
make explicit is that "claiming authority that is not codified" is
explicitly a thing that will not be allowed in internals discussions
as it seems to keep happening and results in a lot of confusion, and
frustration.

cheers
Dan
Ack

---

## #106411 — Peter Bowyer — 2019-08-07T14:03:23+00:00

URL: https://externals.io/message/106384#106411 · In reply to: #106410

> I think when we adopt a Code of Conduct one of the things we need to
> make explicit is that "claiming authority that is not codified" is
> explicitly a thing that will not be allowed in internals discussions
> as it seems to keep happening and results in a lot of confusion, and
> frustration.
>

Documenting the project structure would also be helpful.

When the PHP Group was mentioned I went hunting for details. I found a list
of names at the top of https://www.php.net/credits.php but nothing covering
what their role or authority is.

Peter

---

## #106412 — Ben Ramsey — 2019-08-07T14:09:26+00:00

URL: https://externals.io/message/106384#106412 · In reply to: #106411

> 
> 
> 
> 
> > […]
> 
> Documenting the project structure would also be helpful.
> 
> When the PHP Group was mentioned I went hunting for details. I found a list
> of names at the top of https://www.php.net/credits.php but nothing covering
> what their role or authority is.


Their “role and authority” is copyright ownership of the “code, text, PHP logo, and graphical elements” of the PHP website. https://www.php.net/copyright.php

Cheers,
Ben

---

## #106413 — Zeev Suraski — 2019-08-07T14:14:38+00:00

URL: https://externals.io/message/106384#106413 · In reply to: #106410

> 
> > […]
>
> Please could you point to where this alleged rule has ever been
> written down or agreed to?
>

There's indeed no such rule that any individuals have a veto power.


> Although certain people may have claimed this is a rule, it's never
> been agreed afaik.
>

I'm not aware of anybody who ever claimed that such a rule existed,
either.  If people are alluding to me - then I don't claim I can veto
anything;  I think it's also clear from what I think about the short tags
deprecation RFC that *if* I had veto power, that would be an instance where
I'd use it.  The reason we went for V2 aren't because of a veto, but
because of issues in the previous RFC.

With that said - the source code of PHP is copyrighted by the PHP Group -
and it's a fact that is mentioned at the top of every PHP source file.  The
PHP Group is mostly inactive, and will likely stay this way, but under some
extreme situations - it might choose to act (if ever - probably primarily
around things that have to do with process).

I think when we adopt a Code of Conduct one of the things we need to
> make explicit is that "claiming authority that is not codified" is
> explicitly a thing that will not be allowed in internals discussions
> as it seems to keep happening and results in a lot of confusion, and
> frustration.
>

The more accurate word here is 'if', rather than 'when'. But I don't think
there's a need to wait for a CoC on this one - it should be clear that no
individual has veto powers, but it should be also clear that not everything
is up for a vote.

Zeev

---

## #106414 — Ben Ramsey — 2019-08-07T14:16:02+00:00

URL: https://externals.io/message/106384#106414 · In reply to: #106412

> 
> 
> > […]
> 
> 
> Their “role and authority” is copyright ownership of the “code, text, PHP logo, and graphical elements” of the PHP website. https://www.php.net/copyright.php


Clarification: I didn’t mean to imply just the PHP website. I meant the entire part of the PHP code base that is covered by the PHP license. https://github.com/php/php-src/blob/master/LICENSE

Cheers,
Ben

---

## #106415 — Peter Kokot — 2019-08-07T16:45:09+00:00

URL: https://externals.io/message/106384#106415 · In reply to: #106413

>
>
>
> 
> > […]
>
>
> There's indeed no such rule that any individuals have a veto power.
>
> > […]
>
>
> I'm not aware of anybody who ever claimed that such a rule existed, either.  If people are alluding to me - then I don't claim I can veto anything;  I think it's also clear from what I think about the short tags deprecation RFC that if I had veto power, that would be an instance where I'd use it.  The reason we went for V2 aren't because of a veto, but because of issues in the previous RFC.
>
> With that said - the source code of PHP is copyrighted by the PHP Group - and it's a fact that is mentioned at the top of every PHP source file.  The PHP Group is mostly inactive, and will likely stay this way, but under some extreme situations - it might choose to act (if ever - probably primarily around things that have to do with process).
>
> > […]
>
>
> The more accurate word here is 'if', rather than 'when'. But I don't think there's a need to wait for a CoC on this one - it should be clear that no individual has veto powers, but it should be also clear that not everything is up for a vote.
>
> Zeev
>

Veto has been mentioned here
https://externals.io/message/105201#105558

I'm not having any issues with veto being used here or not on a
previous RFC from people that are in the internals since day 1. I
think we should respect that they have issues with proposals coming up
in recent years, but hopefully group will also understand us - users
and new contributors a bit that we just want to have a bit of cleanup
of legacy things here and there :)

Thanks and have a nice day.
-- 
Peter Kokot

---

## #106416 — Chase Peeler — 2019-08-07T16:56:06+00:00

URL: https://externals.io/message/106384#106416 · In reply to: #106415

> 
> > […]
> wrote:
> > […]
> either.  If people are alluding to me - then I don't claim I can veto
> anything;  I think it's also clear from what I think about the short tags
> deprecation RFC that if I had veto power, that would be an instance where
> I'd use it.  The reason we went for V2 aren't because of a veto, but
> because of issues in the previous RFC.
> > […]
> - and it's a fact that is mentioned at the top of every PHP source file.
> The PHP Group is mostly inactive, and will likely stay this way, but under
> some extreme situations - it might choose to act (if ever - probably
> primarily around things that have to do with process).
> > […]
> think there's a need to wait for a CoC on this one - it should be clear
> that no individual has veto powers, but it should be also clear that not
> everything is up for a vote.
> > […]
>
> Veto has been mentioned here
> https://externals.io/message/105201#105558
>
> I'm not having any issues with veto being used here or not on a
> previous RFC from people that are in the internals since day 1. I
> think we should respect that they have issues with proposals coming up
> in recent years, but hopefully group will also understand us - users
> and new contributors a bit that we just want to have a bit of cleanup
> of legacy things here and there :)
>
> Thanks and have a nice day.
> --
> Peter Kokot
>
> --
> 
> 
>
> What powers are available, and to whom they are available, is probably
something that should be moved to another thread. We currently have at
least three different discussions going on in this thread:
1.) The RFC itself
2.) Default handling of the ini setting
3.) Whether certain people can veto RFCs.

To address Andrey's initial concern, which is currently leading to him not
voting:

Nobody is vetoing anything. Due to both the procedural issues (the way the
voting was structured with two options) as well as the severity of the
issues raised after the voting, another RFC was proposed that supersedes
the original RFC. The procedural issues alone were enough to warrant
another vote on an RFC that had fixed those issues. This means that, for
all intents and purposes, the first RFC never existed. If the current RFC
passes, then it will be implemented as proposed. If it fails, then
treatment of short tags will remain as it currently is.

I hope you will reconsider your decision to not vote on this new RFC. I
understand your concerns. As someone that didn't like the outcome of the
first vote either, I also didn't feel that a revote just because a lot of
people decided to speak up after the fact was the correct course of action.
I don't think that is what is happening here, though.

-- 
Chase Peeler
chasepeeler@gmail.com

---

## #106417 — Peter Kokot — 2019-08-07T17:00:12+00:00

URL: https://externals.io/message/106384#106417 · In reply to: #106416

Hello.


>
>
>
> 
> > […]
> What powers are available, and to whom they are available, is probably something that should be moved to another thread. We currently have at least three different discussions going on in this thread:
> 1.) The RFC itself
> 2.) Default handling of the ini setting
> 3.) Whether certain people can veto RFCs.
>
> To address Andrey's initial concern, which is currently leading to him not voting:
>
> Nobody is vetoing anything. Due to both the procedural issues (the way the voting was structured with two options) as well as the severity of the issues raised after the voting, another RFC was proposed that supersedes the original RFC. The procedural issues alone were enough to warrant another vote on an RFC that had fixed those issues. This means that, for all intents and purposes, the first RFC never existed. If the current RFC passes, then it will be implemented as proposed. If it fails, then treatment of short tags will remain as it currently is.
>
> I hope you will reconsider your decision to not vote on this new RFC. I understand your concerns. As someone that didn't like the outcome of the first vote either, I also didn't feel that a revote just because a lot of people decided to speak up after the fact was the correct course of action. I don't think that is what is happening here, though.
>
> --
> Chase Peeler
> chasepeeler@gmail.com

Just to be more clear here. If the RFC fails then the short opening
tags will stay in PHP for ever. I'm not sure what will change in 5 or
10 years so much so considering the feedback I think we should then
leave them in for ever and enable them by default everywhere and have
two PHP opening tags. Yes, this is what happens when there is no plan
from key people involved here.

-- 
Peter Kokot

---

Next page: https://externals.io/message/106384.md?page=2
