Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:121462 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 72826 invoked from network); 25 Oct 2023 11:58:51 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 25 Oct 2023 11:58:51 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 422961804F5 for ; Wed, 25 Oct 2023 04:58:51 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_40,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-pj1-f47.google.com (mail-pj1-f47.google.com [209.85.216.47]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Wed, 25 Oct 2023 04:58:50 -0700 (PDT) Received: by mail-pj1-f47.google.com with SMTP id 98e67ed59e1d1-27d18475ed4so4334171a91.0 for ; Wed, 25 Oct 2023 04:58:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698235129; x=1698839929; darn=lists.php.net; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=93UhbdQ4Lead3G3hhEA0eRTgmzM8pmRoyzEQlxSaivg=; b=j9dsYgfUxTWZ31OEpuxBk747rhCK4bmeOs8v+ry+B/60v/NSaR9JqqLHC/dHXL9Zdp vxNxqpuLqy74aYhHczq4229yVKrgSqBxY2S8PVuOOZhQHqkv06iAb4gvg6i9remJPGhz sPBJIRdt9+uudVIS9rG7KlX3q5LpBlcK+bz6jSAC2erQitRAQvFP+cgx0NmkFuI0fCFB ZtBqp37+5ljLVspWezIJZHaFQhvVOfmr08ytqAa44Y9JbcIEaC7VEI4wJu4zQsC4suJD 3mBre5M7URMJsxOGKzMsfpt9HvXBqoybuuAJ4MajAfe/C2KeCZv/r46Cwp3RnDwdeVmJ rgPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698235129; x=1698839929; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=93UhbdQ4Lead3G3hhEA0eRTgmzM8pmRoyzEQlxSaivg=; b=MCYtUJr5YyKtZoGHMYg0uZ5c3+wly9+8tUBGFCQ/04eFjyMomraP/vUD2Uhpu/dJ6h mGI2GV6csiaGf6MoneSvIXvT9LJDzDkkmMuDJ80M0O5QwvY3FsX6Z51EVT/tmGK998jN L8F/8+Nv4AT/bjmDWgWLSoquZVMq689rmzLkiq/L5Hiu9VHQV5npuj/n7CNc3TWSkk18 TZ8Q6JVuHNNIPZwQrRZT4QjvpGYM3eLUeZJ/Jbo7zLRHo0DRmhpWxYJxCbQ03rPt5HK+ Hb7BNegp8wWiVz/GLNmfkpw6qztrgfuVcb6rzXkAHACLopkJcGJX3hAdzGsNf8I05eaC Vpzw== X-Gm-Message-State: AOJu0Yw4FJd+41XrQ1w91tZf820sbU2WM5RQ7YsRrohw604zUOCkULol ZwDi3U6KqrrQDtpv9cJXqtnHiiqgS+6f8imQuyM= X-Google-Smtp-Source: AGHT+IEQ4kl9J5rqljQJNkuB1vO9Zu+4RquJ+PWM22zHEkDVfX9QM4uD94SoK7NoX5RcQRrXheTajkfnEHzSn0v+CK0= X-Received: by 2002:a17:90a:d996:b0:27d:546b:4258 with SMTP id d22-20020a17090ad99600b0027d546b4258mr12868948pjv.31.1698235129560; Wed, 25 Oct 2023 04:58:49 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 25 Oct 2023 12:58:38 +0100 Message-ID: To: someniatko Cc: php internals Content-Type: multipart/alternative; boundary="000000000000a484e20608892d0d" Subject: Re: [PHP-DEV] Custom object equality From: george.banyard@gmail.com ("G. P. B.") --000000000000a484e20608892d0d Content-Type: text/plain; charset="UTF-8" I am just going to put this out there, but I will vote against any RFC which provides access to userland to overload == and <=> until the base semantics of PHP comparisons are fixed and the necessary engine prerequisite work is done. I am working on such an RFC, as I frankly do not trust people to think stuff through and handle things like polymorphic comparisons. Also, introducing some new kind of weird operator is just... bad. Best regards, George P. Banyard --000000000000a484e20608892d0d--