Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119084 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 34819 invoked from network); 4 Dec 2022 04:09:13 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 4 Dec 2022 04:09:13 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E4264180054 for ; Sat, 3 Dec 2022 20:09:12 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,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-lf1-f49.google.com (mail-lf1-f49.google.com [209.85.167.49]) (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 ; Sat, 3 Dec 2022 20:09:09 -0800 (PST) Received: by mail-lf1-f49.google.com with SMTP id p36so9163399lfa.12 for ; Sat, 03 Dec 2022 20:09:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ManHuaBYEgaVq1GAeY3mn23m+s308iH1L9dBKSnESiI=; b=Y128JBKcjYAUNJeUckwRpMNqukHZkIjRWSjRgM0BRbV7/Hnkm5JUkAV70q6KG9A9ej lffOkTsuKyyU2URzEtkxgGAia7HhBYeWX+G9HkCbF2QfOWipoF8YaLS9LcWittRCA6zk lDkY914OqZzMqwDhVJUCLFHpJ7Tks4iksRGBbdPty5dDmK156Cp4VtrYxtaO+p9Zv5D0 RpobFADn2P0VVOuLZpQknpHIuaYU4OSIXUn/zNE4M5RfRMwbSJfeU+CPror5ewDTiZg3 cOHlFFP8xainwPBdvF3609tqj31lrf6UXhMXbLS+FleLwmSV1PnHF+OVF9K7wB5IvWuT YKfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=ManHuaBYEgaVq1GAeY3mn23m+s308iH1L9dBKSnESiI=; b=zQ22bld1Ch1qFxl1WXTNCYQ9nhDnH19b30BXOpEDDteQ+G4jOOavsjBCquUsKXeNp9 dbjcm0UL1wjo2Dg2qTXAexOx9z7z2wxpvfzcjaI8FqNVhGJvgAucYwSDRZBQhANBSN3+ 2gKIAKNEXdUtSECdfCk8ByCuloJbePQnRa0AZ9Kxty6WwRHsl18pPvDqyvxm5LBiQGBf lToKswzFZm2ZdOa/UWNXpd2b6aNEeZ2ce+X0WO70oRaBkPN6HDIdw2epjzjfMBuE0Qey hinNBfAZtZPL3b2jDku7WHgQRHtWNWi7/oJs5E6dZ8ZARAAhgTULJBEuyr5wfQdOLnQQ DnOQ== X-Gm-Message-State: ANoB5pmKv3rsVrB0M8SSj51F7Jtg8E6vb9Jgcw2G59t7xLLpMfbxshXr UA9lXqVVDq7nbr/o8YDpLGmOvtPt2uVEehYz7TQ= X-Google-Smtp-Source: AA0mqf7+Vlxy03AnlguCPjeujfSDMsCxSSWiXQe+uQD7YD1UBy06YoOYl6rY2YhtfFaJKEPYANecnBue9BtZTXs/DPE= X-Received: by 2002:a05:6512:749:b0:4ae:d0fc:1bce with SMTP id c9-20020a056512074900b004aed0fc1bcemr24371945lfs.107.1670126947611; Sat, 03 Dec 2022 20:09:07 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Sun, 4 Dec 2022 05:08:55 +0100 Message-ID: To: Karoly Negyesi Cc: Marco Pivetta , PHP Internals List Content-Type: multipart/alternative; boundary="000000000000713a6605eef8bbe0" Subject: Re: [PHP-DEV] Please allow an out of readonly properties From: glash.gnome@gmail.com (=?UTF-8?B?TcO2bsO0bWUgRXBzb24=?=) --000000000000713a6605eef8bbe0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, You can always patch PHP. In what context do you use reflection ? It's quite easy to override the behavior of readonly. Do you need readonly behavior ? Le sam. 3 d=C3=A9c. 2022 =C3=A0 23:56, Karoly Negyesi = a =C3=A9crit : > They refuse to compromise even on documentation issues. I am totally > helpless. Not sure what could be done? > > On Sat, Dec 3, 2022 at 2:48 PM Marco Pivetta wrote: > > > Talk to the designers then: bringing your own political issues up to th= e > > programming language/tooling only makes it worse long-term, for everyon= e > =F0=9F=98=9B > > > > On Sat, 3 Dec 2022, 23:45 Karoly Negyesi, wrote: > > > >> I do not have the luxury of designing my own system. I am forced to us= e > >> upstream. I can't help it and given the history of private usage and t= he > >> refusal on relaxing them I do not see this improving with the readonly= . > At > >> all. > >> > >> On Sat, Dec 3, 2022 at 2:42 PM Marco Pivetta > wrote: > >> > >>> Terrible idea: reflection is mostly introspection tooling, and doesn'= t > >>> really bend the rules of the type system, other than crossing scope (= it > >>> "sees" more). > >>> > >>> Please consider designing your system to consider the constraints of > >>> `readonly` properties, or design the constraints to fit your system > instead. > >>> > >>> Marco Pivetta > >>> > >>> https://twitter.com/Ocramius > >>> > >>> https://ocramius.github.io/ > >>> > >>> > >>> On Sat, 3 Dec 2022 at 23:39, Karoly Negyesi > wrote: > >>> > >>>> Hello, > >>>> > >>>> If push comes to shove, private properties can be changed with > >>>> reflection. > >>>> > >>>> Readonly properties can't. > >>>> > >>>> Please add a readonly toggle to reflection. > >>>> > >>>> Thanks > >>>> > >>>> Karoly Negyesi > >>>> > >>> > --000000000000713a6605eef8bbe0--