Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113642
Message-ID: <EA5B51DE-ACCE-448B-9232-D882F59D8966@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_79A017AA-3756-4F3D-BFD5-2218848A0A3B"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Sat, 20 Mar 2021 19:58:21 +0100
In-Reply-To: <CAF+90c9_=GkKbErf-z464_zqAHCDERbdLjd_uyoNvC9PERxoxQ@mail.gmail.com>
Cc: =?utf-8?Q?Alexandru_P=C4=83tr=C4=83nescu?= <drealecs@gmail.com>,
 PHP internals <internals@lists.php.net>
To: Nikita Popov <nikita.ppv@gmail.com>
References: <CAF+90c-HY-0fx+pTmntRJZKcQcZFfk3uJwrZ6FAMAx5_Wj+JHw@mail.gmail.com>
 <CAAwdEzApyQd52RpJ-gW+pNtBA=jA1bn74c-K1djcztRRgaYAag@mail.gmail.com>
 <CAF+90c8YMpGNLKehfFW6gWJx0mGUVqL0Rx+U262gGRP6cTXBgw@mail.gmail.com>
 <CAAwdEzDwD5sc6AQxLSnj0Dx=4ZsP1h0K83TS+jyN1x5_X7NAAg@mail.gmail.com>
 <CAF+90c9_=GkKbErf-z464_zqAHCDERbdLjd_uyoNvC9PERxoxQ@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] New in initializers
From: claude.pache@gmail.com (Claude Pache)

--Apple-Mail=_79A017AA-3756-4F3D-BFD5-2218848A0A3B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> Le 19 mars 2021 =C3=A0 12:22, Nikita Popov <nikita.ppv@gmail.com =
<mailto:nikita.ppv@gmail.com>> a =C3=A9crit :
>=20
> I've updated the RFC (and implementation) to evaluate class constants =
and
> static properties at time of class declaration. As such, everything =
should
> have a well-defined evaluation order now.
>=20
> However, this also means that this RFC now also contains a
> backwards-compatibility break: Anything used inside class constant / =
static
> property initializers needs to actually be available at the time the =
class
> is declared. You can't first declare the class, then declare some
> additional constants it uses, and then use it.
>=20

I don=E2=80=99t like having the static property initialisers and =
constants evaluated eagerly. I typically declare the main class followed =
by zero or more class helpers in the same file: with the proposed =
semantics, I may be forced to occasionally reorder my code. One =
particular case I have in mind is the following refactoring that I may =
perform with the advent of enums:

```php
class Foo {

    const STATE_OPEN =3D 1;
    const STATE_CLOSE =3D 2;

    function setState(int $state) {
         // ....
    }
}
```

into:

```php
class Foo {

    #[\Deprecated] const STATE_OPEN =3D FooState::OPEN;
    #[\Deprecated] const STATE_CLOSE =3D FooState::CLOSE;

    function setState(FooState $state) {
         // ....
    }
}

enum FooState {
    case OPEN;
    case CLOSE;
}
```

=E2=80=94Claude



--Apple-Mail=_79A017AA-3756-4F3D-BFD5-2218848A0A3B--