Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126023
Message-ID: <19332d18-9b15-4bc6-9981-932c1179267e@gmx.de>
Date: Thu, 21 Nov 2024 12:54:16 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] Deprecate alternate switch case syntax?
Content-Language: de-DE
To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>,
 Derick Rethans <derick@php.net>
Cc: internals@lists.php.net, Theodore Brown <theodorejb@outlook.com>,
 Kamil Tekiela <tekiela246@gmail.com>
References: <PH7PR16MB5781B1CEDD5B86B51C7CD088DE212@PH7PR16MB5781.namprd16.prod.outlook.com>
 <CAGBsUrfQs7W0x7cM+KWtFi5j8pS9fmA8B=ZByc1jwhpEjpxyuw@mail.gmail.com>
 <PH7PR16MB5781DD152F681DD3F15A57CADE212@PH7PR16MB5781.namprd16.prod.outlook.com>
 <943CFFC1-B0F8-4326-BF2E-138BC1E48DB7@php.net>
 <4b592cbebc0dcb6bcd66f3ef75e9d847@bastelstu.be>
In-Reply-To: <4b592cbebc0dcb6bcd66f3ef75e9d847@bastelstu.be>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
UI-OutboundReport: notjunk:1;M01:P0:ym7QubqFb5M=;A8kZGkdyjO/YEHF3Xg6ndSe7HIu
 osrkDQAgq1KozFlreCS9g4+tquNj43qRhN2ayy8fGu/3UqVhNNsFmLhd28zuXecSQlhYkjH7h
 1eamP0muUhFqiiU+dFh7XbxHe+drXWlX9yw4ajUG2sDgfYMO5Vz/NHHpcqEMffaZIMImVFPfv
 j7Q4MknpSdejIlyl/rKRiIy4chxtRtHLjLhXqAD9rBUCBGQDnix+f5ExdgsJoqo8YzgU8bFnu
 1l0LX9wVaX25/0etTXKsfNCq3W1Atx96ipbynOEUMYAW9J/g1qWZMNs0W2ZkiLVgN0DAzqnM2
 +OLcQreYET5Itu/VpR6UBTTHmAS2LunyEs36eu65xK9zuaBEDr1gswtNlLY4887G8VZnMAZ/W
 UD4HOP3rfO2Dl3v6bXOcF0YCMhEomfndKb94IQ7Jwf6kdCkhbAnMnnwiurcLHB0ypRGoZw3LT
 sWfk4gjsr4fCz1aeC1hu1QjbuTJk9j5MNJPFBcUQE1+/uTlGE+6nMjJpd/jnHIGqq+4qmeqV0
 x6KQZ8WkogdL+zA4bDb5OMx5QaoA77aFE/eRmxZJ098it0pe3o+yBpxcXHQWFtE7XVwkapQmU
 BebvZE1gziNHeaykTrB6Mchw9pUpK67Gnag09ANIUBXHs4hmON6j0aUfs0eRIi7hjjThAUp2R
 oP4cLZrLseL7yZt2ZEsK82JA6UwD44o7b6lbQXxWTv3ZGWsjUabqMn2FmovFvNmgFgMhUO/w8
 pwL4fTjY2skjYnPCC/u0HtaTrw8ntIEj4EMyACjPotUQWnKZBFNWr7/rSxqBQfrM4YCBQBYMw
 pTnqVRybKHyNRG2HZP9CDlCYlLjTyONetO2YhCs1UzhEBgmTY0Cdk5IA303shWO9aAjLmoNck
 oafZKiytS6sWvQVJEEsglYyjv7kA0Ml7BmSVPMKmOFjPtNPmYyhh/OJ0z
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 21.11.2024 at 10:36, Tim D=C3=BCsterhus wrote:

> This proposal would not affect that. You would just need to add a colon
> after the `case` statement, not a semicolon. In fact that would more
> closely match the corresponding `switch`, which would also need to have
> a colon:
>
> =C2=A0=C2=A0=C2=A0 <?php $foo =3D "bar"; ?>
>
> =C2=A0=C2=A0=C2=A0 <?php
> =C2=A0=C2=A0=C2=A0 switch ($foo):
> =C2=A0=C2=A0=C2=A0 case "bar":
> =C2=A0=C2=A0=C2=A0 ?>
> =C2=A0=C2=A0=C2=A0 BAR
> =C2=A0=C2=A0=C2=A0 <?php break; case "baz": ?>
> =C2=A0=C2=A0=C2=A0 BAZ
> =C2=A0=C2=A0=C2=A0 <?php endswitch; ?>
>
> Though using `switch` in such templates is somewhat finicky anyway,
> because it will need to be merged with the first `case`, because otherwi=
se:
>
>> Parse error: syntax error, unexpected T_INLINE_HTML "", expecting
>> "endswitch" or "case" or "default"

There is no parse error if you use PHP snippets in such templates like
you use C preprocessor directives (i.e. always starting at the first
column); e.g. https://3v4l.org/cK0Ll.  Or see https://3v4l.org/7mKS8,
which is how I would write it, if I was using switch statements in such
templates.

Note that I'm not advocating to keep the behavior, but I also don't see
how it would be harmful.  Without an enforced CS, there can be more
confusing code anyway.

Christoph