Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121429
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
In-Reply-To: <CABAhh3FtvJ3TMF6R8Ot1o+OzS+SMOw37U3uehgCWPrP7guHB1A@mail.gmail.com>
Date: Thu, 19 Oct 2023 11:07:54 +0100
Cc: php internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EF81B241-AA0F-4888-9CB9-46E08C90664B@craigfrancis.co.uk>
References: <CABAhh3FtvJ3TMF6R8Ot1o+OzS+SMOw37U3uehgCWPrP7guHB1A@mail.gmail.com>
To: someniatko <someniatko@gmail.com>
Subject: Re: [PHP-DEV] Custom object equality
From: craig@craigfrancis.co.uk (Craig Francis)

On 18 Oct 2023, at 13:50, someniatko <someniatko@gmail.com> wrote:
> There were already suggestions on the mailing list to allow =
"overloading" existing `=3D=3D` operator, and some suggestions went even =
as far as overloading `<`, `>=3D` etc operators.


Slightly off-topic, but concatenation?

Just as a possible feature... for my sins I'm the database component =
maintainer for WordPress, and I'm currently getting `wpdb::prepare()` to =
work with the `literal-string` type, where I added support for escaping =
identifiers (field/table names). This function works like `sprintf()`, =
with the SQL being the `$format` argument, and then user values; from =
that it returns an SQL string with escaped values (yes, I know, =
parameterised queries are better, but we work with what we have)... =
developers often concatenate these together, but I was wondering if I =
could return a stringable value-object, so when they are concatenated, a =
new value-object could be created instead, so we can verify (ideally at =
runtime) that all values have been escaped correctly (and maybe use =
parameterised queries).

Craig=