Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130000
Content-Type: multipart/signed;
	boundary="Apple-Mail=_F085F138-6CF7-4E04-BA2C-8FB5705B1F1C";
	protocol="application/pgp-signature";
	micalg=pgp-sha256
Precedence: list
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.300.41.1.7\))
Subject: Re: [PHP-DEV] [RFC] Trailing Boolean Operators
Date: Tue, 3 Feb 2026 19:57:34 -0600
References: <CAEwAiAFGGCiyR1dWPUDhFkjLpfYk7TsWgXWeixeQM=qqZhEkSQ@mail.gmail.com>
 <20260204011317.E86B61A00BD@lists.php.net>
 <CAEwAiAEOLkw1a0uGKwMZfjqQEA7qjMfhQw_sTRyU3nENJ26a9Q@mail.gmail.com>
To: Len Woodward <len@artisan.build>,
 php internals <internals@lists.php.net>
In-Reply-To: <CAEwAiAEOLkw1a0uGKwMZfjqQEA7qjMfhQw_sTRyU3nENJ26a9Q@mail.gmail.com>
Message-ID: <D1ED4C59-495A-474A-9ACD-96F6B17097D5@php.net>
From: ramsey@php.net (Ben Ramsey)


--Apple-Mail=_F085F138-6CF7-4E04-BA2C-8FB5705B1F1C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

This message went directly to me instead of the list, so I=E2=80=99ve =
added the list back to my reply.

> On Feb 3, 2026, at 19:35, Len Woodward <len@artisan.build> wrote:
>=20
> I had originally written this RFC in markdown, and when I had claude =
migrate it for the wiki it discarded a whole section I had in there =
about simply using leading operators instead. I've added that back in =
and tagged a minor change.

Pro-tip: pandoc can do Markdown-to-Dokuwiki conversion in a =
deterministic way, so you don=E2=80=99t have to worry about LLMs =
generating slop.

    pandoc -f markdown -t dokuwiki my-doc.md

https://pandoc.org/=20

> The gist of the argument against simply using leading operators =
instead is that it doesn't solve the problem -- It just moves it. =
There's always going to be a special reordering case.

I see this as a feature and not a bug. Boolean operators control program =
flow. Whenever you add a new condition, you should have to think about =
reordering (because you might really need to reorder the conditions), or =
you should consider splitting up the logic so that it is more =
maintainable.

> ps. When replying to the thread, I know I'm supposed to respond =
underneath the previous content, but am I supposed to keep the entire =
history, or just the previous message? I'm rereading the policies and =
the rfc:howto, and I can't find that section.

Yes, you may truncate the original message and weave your reply between =
quotes, as I=E2=80=99ve done in this reply.

Cheers,
Ben



--Apple-Mail=_F085F138-6CF7-4E04-BA2C-8FB5705B1F1C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iHUEAREIAB0WIQToXQMR3fpbrPOmEOewLZeYnIwHGwUCaYKnjgAKCRCwLZeYnIwH
GyxbAP9/+m1CiICS9jSZ0GzY5IQiixpo2eiQlYS8vZi87NwKLwD/Wv0sd+5Tbkqv
TdjgPa/w3ECIFTMGTQtK6e/XQUbzeHo=
=lCh1
-----END PGP SIGNATURE-----

--Apple-Mail=_F085F138-6CF7-4E04-BA2C-8FB5705B1F1C--