Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116414 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 6734 invoked from network); 16 Nov 2021 14:04:50 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 16 Nov 2021 14:04:50 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id CFF911804C6 for ; Tue, 16 Nov 2021 06:59:47 -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=-0.2 required=5.0 tests=BAYES_20,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 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-lj1-f178.google.com (mail-lj1-f178.google.com [209.85.208.178]) (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 ; Tue, 16 Nov 2021 06:59:47 -0800 (PST) Received: by mail-lj1-f178.google.com with SMTP id 13so43902019ljj.11 for ; Tue, 16 Nov 2021 06:59:47 -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=tYeWtaLmIrCwV1k3j4m+SpsraMxXDl+JOlHeCI9OFD8=; b=JXeaPmiu73xuuShyd5FrvEtPazC4LL1FOg/LxMZY/18vpCjCJpOsSJ/oyEkeHnTfe2 UsbOodzoaYdp+mMXblCaKvD3mb7nG0oKfjRPhTS2dSnO3yAuOofw2LURtcb5bsApp0Lc 8nfd4hXpf/u0pgM2tzGJdiO3hPWUH+1kYpARPqlJGPi2rJpQBya3FxfWb0KbwYjW+loi nPranx73ls+YZfNa3LaQJuLYtY+VR1rmH34INC2ZHlYx+gWJ6/oofjDSxW8BqBUOwIJ2 J80LyaU4aTiZAadCYXFhqYE6b3PaDAllzArTYcmNIzhoqvKQSZk9t5xrbkjIF5dem7tX Z9kw== 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=tYeWtaLmIrCwV1k3j4m+SpsraMxXDl+JOlHeCI9OFD8=; b=5sBUJEzQCjwxBtdtfckVr4MCeYYqyRPvfj6acx851Pvrra7oPij6zfYKdz5d+f0gro 06oKCWXuVT2BN3X1t5JFoRHYmhHzuQYZuVYsMhqHw2AwzhhCOzA8t3zHmkGytxo6X0Ab RNirE7CPCKcuApchkJPdnZ3YMu/duRGpniBETqKnwaGtGgSCDte+8tcO6Ln7XoY7Zpel XRtelsSfIM/s/qGKldc7EC8yfGS3EzyD8tzLsHO0lep3ygE2jkZ4v48W/TZoQQjUarS2 G3PSNwJ1UJBnDEAJBavj9o9pLUBuAUGn2iqBlVtgzFeoEDOT7KbYD7EEMqtNWuaX1n3t 39SQ== X-Gm-Message-State: AOAM530Ik1A5FxlCs1pHke0rVanlyIIRPG6hmUDad+ZDczwjHSab257t SowuHsdvL2cfcgMEPN9b5kLDsyQQIOAWFhHS0QY= X-Google-Smtp-Source: ABdhPJy53emcVOsQkkIvneT8QQFYYV/iI3E1j2K+3M4yJlMj0+JVx16dtQ6ossYbNTQO6uJs8YHsoZdEac0lfNyaz5Y= X-Received: by 2002:a2e:9601:: with SMTP id v1mr7959358ljh.478.1637074785763; Tue, 16 Nov 2021 06:59:45 -0800 (PST) MIME-Version: 1.0 References: <371ca983-2b07-ae39-3629-49cf7ff8ee64@heigl.org> <497ab532-a39d-389c-8bca-86768650c2f4@heigl.org> In-Reply-To: Date: Tue, 16 Nov 2021 08:59:34 -0600 Message-ID: To: Rowan Tommins Cc: PHP internals Content-Type: multipart/alternative; boundary="00000000000013849505d0e92d9d" Subject: Re: [PHP-DEV] Re: [RFC] Deprecate dynamic properties From: neclimdul@gmail.com (James Gilliland) --00000000000013849505d0e92d9d Content-Type: text/plain; charset="UTF-8" On Tue, Nov 16, 2021 at 4:23 AM Rowan Tommins wrote: > On 16/11/2021 09:27, Andreas Heigl wrote: > > > >> I see, yes, code that is 100% perfectly tested can get away without > >> the language performing any error checking at all - the behaviour is > >> all guaranteed by the tests. I would be very surprised if even 1% of > >> PHP applications can claim such comprehensive tests. > > > > The topic here was that new code can verify the declaration of a > > property by using tests. That does not need to happen on the language > > level. I was never talking about adding tests for existing code. > > > > For most code bases, even new ones being written from scratch in PHP > 8.0, that level of testing simply doesn't exist, and having the language > tell you "hey, you wrote $this->loger instead of $this->logger" is a > useful feature. And, in a lot of cases, more useful than having the > language say "OK, I've created your dynamic $loger property for you", > which is what currently happens. > What you described there sounds like a warning and not a fatal error. Maybe that's where some of the trepidation is coming from. I know I'm less worried about the deprecation notice and more worried about what happens in PHP 9 when it's a fatal error. --00000000000013849505d0e92d9d--