Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119738 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 9573 invoked from network); 17 Mar 2023 13:32:56 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 17 Mar 2023 13:32:56 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E1BAD180381 for ; Fri, 17 Mar 2023 06:32:55 -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.7 required=5.0 tests=BAYES_05,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, 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-pf1-f182.google.com (mail-pf1-f182.google.com [209.85.210.182]) (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 ; Fri, 17 Mar 2023 06:32:55 -0700 (PDT) Received: by mail-pf1-f182.google.com with SMTP id fa2so1511090pfb.7 for ; Fri, 17 Mar 2023 06:32:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679059974; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=4Ju7mTbpTxDgGetCy7zBNJsVQYX17HCP2KCwxILu2pQ=; b=QtYM61Oxseb4d+qaKLPqgl6C8fXMviOQ8Q7ejY6tzdO86o+jBQNS7HnvCI5VRvRmDo 5Hpiiv16iY5uHxDqSoY3kx+BRQxvy4CFoGjhyJ993mr61eNaNTEhbnNMwBe8EFqtBlI7 e//MZU2FOn3emvspfxx86HK8hkfs5SPRHQyvoWG/pWoNffoUuowUFApr2s8Ak5PYu5Tm HGDgzcmKo0bRiNPrgS0PxFxYSVt8lqzQW0auTV0phQeJo/Yj4M6s6/518qbiZpHdQ/hQ m6qqNhrpftQKbXqE+rvK7lDHUt6h+hZjlQeYMfUIwL5kRZW++kthhoRnHuDAbjQb/Xrm /LkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679059974; h=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=4Ju7mTbpTxDgGetCy7zBNJsVQYX17HCP2KCwxILu2pQ=; b=iYylTLA7pGw9RyTFqt6dxVR7tEbzAY3uUjteEzSpyhnHzlp5JtrWrHcSBj5hj8rJ+U AS2ACh6j8NGRFk6zrjmlVOsxqRdojHIAPyoccQ1WmPRPtKymVsn7wWdpfXU1If34wQWk H9k1dmM8xgZta4Me/MJ2eB1mZrU5/Q0Fmx7qzdWe/zxpXDhMjTA0QHk4jdh6+3CRLbhZ 5fVSXL81EmlUj1Tpn3p+TJDJ2NukKtrloUQ7jhmRWpe6EpZY2shZaQ1ANnIbKRrOxIQ4 LfhEWvZ5EwVyGdYd6ZuvsYUklCcAgZzQ/vhteZohzPU60g6qL1CyjDJ+oyTr5bTjUYIk rVFg== X-Gm-Message-State: AO0yUKWDKeT1pQEIOjRZMyQSPBU9Uizw9emScZv9NFr62se/1ulJZ7SY pse32bIov61C47HPt7H5e4oYhyd90HwM3Q7K+K82iuqJYn4= X-Google-Smtp-Source: AK7set+Ca4sT2q8kbXx+J/rsTkAkUz8ffTtqM6H1D9heC44wxVSiAGsulxOCkP0rSdrlaWZXl5mg1H4nl/2lcfO6bvc= X-Received: by 2002:a05:6a00:1990:b0:625:ccb3:7132 with SMTP id d16-20020a056a00199000b00625ccb37132mr3294262pfl.5.1679059974044; Fri, 17 Mar 2023 06:32:54 -0700 (PDT) MIME-Version: 1.0 References: <57ed96c2-0547-c905-1c6f-7433ecb4a1b5@bastelstu.be> <684c1457-16e1-1cf2-b005-b273ff7e4929@bastelstu.be> <55a0f953-b69d-5762-18f4-2af3159b30dd@bastelstu.be> In-Reply-To: <55a0f953-b69d-5762-18f4-2af3159b30dd@bastelstu.be> Date: Fri, 17 Mar 2023 14:32:43 +0100 Message-ID: To: PHP internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] [RFC][Vote announcement] Arbitrary static variable initializers From: tovilo.ilija@gmail.com (Ilija Tovilo) Hi Tim > Isn't the destructor+exception example misleading? In that case the > initial value of '$x' is constant, thus it should always be known to > reflection, no? > > Should the example look like this: > > > function foo($y) { > > $x = new Foo(); > > static $x = $y; > > } > > > > try { > > foo(42); > > } catch (Exception) {} > > ? Yes, your example makes more sense. In my old example the value of the static variable was already assigned so didn't prove the point it was trying to make. I adjusted the example in the RFC. Thanks!