Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116366 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 71585 invoked from network); 15 Nov 2021 11:34:43 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 15 Nov 2021 11:34:43 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id CC89A1804BD for ; Mon, 15 Nov 2021 04:29:24 -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=-1.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2, SPF_HELO_NONE,SPF_PASS 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-qk1-f170.google.com (mail-qk1-f170.google.com [209.85.222.170]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 15 Nov 2021 04:29:24 -0800 (PST) Received: by mail-qk1-f170.google.com with SMTP id bk22so16409133qkb.6 for ; Mon, 15 Nov 2021 04:29:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7eEAq3cbsT8If1XGfRLRZfBXoUgSK3Y3GUTVX+2WZQY=; b=TOX4BiZjrTE+Sm15YiQ7SP343miJj0qTTllrF0D8uL3Uzcqiq8N8MjqNJvGm7FkxLu 2I1M9nqKbbYXSprIumgToIP+X6VR9lG9rFp8qsdpo/JhviUIxyXrQ0PV6mZPfuOiqOwZ nGoi7sxtlXKihgboWJiO+DrNxywKuC2C28/oX7EvDIOqQi4D1NPf6g+B/jgw8Bjw/mH+ YSp+Gb7/UjZ9vxJzDfyqUw1Xjw3biKd7IzvYT4d30FSEMOer28XC/eYkyDH1EYRRt6uW jxcrbpOyKezzBeRrCI2YaGdP0r4ZdMS6Xa3ujlMWMLEnlwcdq82B8RZT/c1R3PaiBKqv 38Zg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7eEAq3cbsT8If1XGfRLRZfBXoUgSK3Y3GUTVX+2WZQY=; b=e582/NTVUMhmMRCvWLjcTHU54XHQl6SXTpbFekdDTFC/ivCz4y4bi0gL5GIKzcsDV2 KdGLaDO8gyL3oc39T7NQejl5vKN+R7sbxmVadW8EDkHnJRwAY1wmHnZmMITVGwerfPNO HEAWqd53gb3kVFs6HkuJac1F3DFlgfftYlzCda8tCNX1rhqR9dGcZIIS8TbfwJdcqP++ znS+ziCjYeij4iagNSbteAJcG/jv9z/WKGjhpYQ0o7+v7fKVjeSbLOhI/bJHWhHbZMZe WK83NoJy4DcKdMG23bvd3T3V8+XSq15iR5TmcLKN1pjvDH1Uqaq1JyAZogCiCsAaD8HV DWqg== X-Gm-Message-State: AOAM530ZvGmojcXJVL7ltBGssWnjYRsoDhBfPRlyKw7OupQmwL/lBe3W HhIEOuyIpDMaIVnk43f6w4yCCJazJvU1K+GbBLo= X-Google-Smtp-Source: ABdhPJy9TdicWZ8zG1zY9Qs22IrqqdR4xq4x+VCaxeWN5nOhaYD+SS/vc1/2r3LaHVznPXKCKEki1wNtW09UbdRIBKs= X-Received: by 2002:a37:f90a:: with SMTP id l10mr28748565qkj.402.1636979363752; Mon, 15 Nov 2021 04:29:23 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 15 Nov 2021 12:29:12 +0000 Message-ID: To: Benjamin Eberlei Cc: Nicolas Grekas , Nikita Popov , PHP internals Content-Type: multipart/alternative; boundary="0000000000007b2ec505d0d2f5c4" Subject: Re: [PHP-DEV] [RFC] Deprecate dynamic properties From: tekiela246@gmail.com (Kamil Tekiela) --0000000000007b2ec505d0d2f5c4 Content-Type: text/plain; charset="UTF-8" I would be very sad to see this RFC not go through. I have voted Yes as I believe this "feature":is a bug that needs to be fixed. There is also an opt-in proposed for people who really do consider it a feature. I don't see why it would cause much trouble for maintainers of OSS. At the moment it is proposed to make this change in PHP 9.0, which is a couple years away. That is a lot of time to fix the code. The deprecation message will inform us about the number of uses, whether accidental or intentional. If we decide that removal of this feature would cause too much disruption, could we not have RFC in PHP 8.3 to remove the deprecation? Deprecated or not, I still believe that OSS should avoid dynamic properties. They are really difficult to identify, even with static analysers. Having the deprecation message would at least help us identify where dynamic properties were used, so that we can fix it. --0000000000007b2ec505d0d2f5c4--