Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119711
MIME-Version: 1.0
References: <CAPyj-LDuXQftpyei9pCE0vKoee0fr2GUyTvtbY6NVaSFPs9nWw@mail.gmail.com>
 <20230315121623.GK2480@phcomp.co.uk>
In-Reply-To: <20230315121623.GK2480@phcomp.co.uk>
Date: Wed, 15 Mar 2023 18:17:54 +0100
Message-ID: <CAPyj-LBwbxCEc0oGt+VjF9qhCrHVQxChhB4irREiFK=PQwc=Cw@mail.gmail.com>
To: internals@lists.php.net
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 Alain

> > https://wiki.php.net/rfc/arbitrary_static_variable_initializers
> > https://externals.io/message/118976
>
> Could I suggest that you make something like the following throw an error:
>
> function foo($i) {
>     static  $a = $b + 1;
>     static  $b = $i;
> }
>
> You could try to reorder but what if the second static had been:
>
>     static  $b = $i + $a;
>
> Yes: stupid, but someone will try it.

With this RFC static variables are evaluated in the normal order of
execution. The first statement will throw an undefined variable
warning and result in 1. The second one will be initialized to
whatever $i contains. This is consistent with non-static variables.

Ilija