Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:123590 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by qa.php.net (Postfix) with ESMTPS id B942C1A009C for ; Thu, 13 Jun 2024 01:24:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1718241919; bh=Zc3aeYl0Uc2H/UqSmgaSHimNLxKyv9hsyHMF6vRENrA=; h=Date:To:From:Cc:Subject:In-Reply-To:References:From; b=VDCRb5i2g+TvjMWWIUBUWjiySUx4Lw3YfdnBtEW3N6bPFJR42+GRe6m0m90dZI5fK eooUWrEUaJmNZ8UGEHHpD1c5wbOga11ZdpB0OcZSsVYMygc/Sy9jftS1ZghQLl9y6o Hh4HtQhs/UdnEgyD4H/+r5KaMQ/axmERgRjceKdILsssZldnj0GmVEgKhLbetx9rGm kjIIqVlvvKc2VM/7ULDuyD67xwvt/E4vVw6F4CJ3W9ubRY78AhnznoNhlSrzhf9420 1fQB38FZrN2AuvPuC4kCxBUFxv7Rh+5olKtWyON95srvbXL+wp+DST5gAPVee3T+Nk A71JCJpsBE6xg== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id EA7A5180056 for ; Thu, 13 Jun 2024 01:25:18 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: Error (Cannot connect to unix socket '/var/run/clamav/clamd.ctl': connect: Connection refused) X-Envelope-From: Received: from mail-40131.protonmail.ch (mail-40131.protonmail.ch [185.70.40.131]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 13 Jun 2024 01:25:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gpb.moe; s=protonmail; t=1718241848; x=1718501048; bh=Zc3aeYl0Uc2H/UqSmgaSHimNLxKyv9hsyHMF6vRENrA=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=mTq8L1wAeQwYYcqHz+Ah/nPQ5E+Bk5oaMLN+EK33aQV5Pz2gNLYHIroXOrfdbz/vN 0ZQV/6aZdt9OiBFQrEw2NGydsG4jrIBP1ORdnp7VvnZuDF2aTYeyl+wtR3csGn07mz 0B6nZ+4NuFL4b04Qxw0ffvJKvQUTnsZ4Fvg/ac2xT7vBnu+inMl9uvrDJICvIyKxav Y4S7c06JtBj60Fi2DYpoHep4spIHFSM5BtFBkIy9e7XhHlakk8D+5r61+jmrLB9wk6 FJVjASpmCnsNTjyybv9nIeqa3KhHVkmfYPqlIge2lOMnogAfFyxtpBPZ6ZBJw5O+IQ K9JqWgLVcl3UA== Date: Thu, 13 Jun 2024 01:24:05 +0000 To: Ilija Tovilo Cc: PHP internals Subject: Re: [PHP-DEV] Property hooks, and &get-only write behavior Message-ID: In-Reply-To: References: Feedback-ID: 96993444:user:proton X-Pm-Message-ID: 0ccd153e989df4d9150f03420e1a0c0ca78baed8 Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: internals@gpb.moe ("Gina P. Banyard") On Wednesday, 12 June 2024 at 16:06, Ilija Tovilo = wrote: > Hi everyone >=20 > [...] >=20 > I hope that these semantics are acceptable for everyone. >=20 > Ilija Hello Ilija, I might know what sort of technical issues you've been running into, as I h= ave some similar issues correctly handling references with my Container/Off= set RFC implementation. The way I'm handling this is by splitting the "get"/read handler/hook to *j= ust* be a by-value return, and for fetching creating a new "fetch" handler = that is called in the respective situations. Therefore, I am wondering if it wouldn't possibly make more sense to add a = "fetch" hook, and ban returning by-ref for the get hook. Best regards, Gina P. Banyard