Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113037
Message-ID:
 <VI1PR02MB4703D332C7B2E2D86FC6D1FEE2B69@VI1PR02MB4703.eurprd02.prod.outlook.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_13145F0C-430A-49F5-A6B3-8AA7169527FC"
Date: Mon, 1 Feb 2021 16:20:58 +0100
In-Reply-To: <ffd16d04-498b-46ac-95e7-b4692900a6d3@www.fastmail.com>
Cc: php internals <internals@lists.php.net>
To: Larry Garfield <larry@garfieldtech.com>
References: <eadd4a32-a05b-463b-a91f-a5d353c577b2@www.fastmail.com>
 <ffd16d04-498b-46ac-95e7-b4692900a6d3@www.fastmail.com>
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [IPv6:2001:7e8:c83a:5400:e90e:fe81:be2c:8c39] (2001:7e8:c83a:5400:e90e:fe81:be2c:8c39) by LO4P123CA0202.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:1a5::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3805.16 via Frontend Transport; Mon, 1 Feb 2021 15:21:00 +0000
X-MS-PublicTrafficType: Email
X-IncomingHeaderCount: 46
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-Correlation-Id: 5f7f3073-b2c8-47eb-c782-08d8c6c4fb48
X-MS-TrafficTypeDiagnostic: HE1EUR04HT237:
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info:
	lD2fYROXrTxTsQcaUqCccRfnR2Dke04qS7h6ZzX3s4GyxHYU/nV0dq/ML/6wTlpEm0XYlXvy2Cn0p8uFbp5dZSd8v4NS/f1kg/KO0eO3ZUNsgNg6zWSypS++A/QREDXC37Vn066sdZf3YpCf6MTcHB86dpS7y4VKJHKWCw33Xn2tHgZr3XNz239TxlNT0gU0zEIVjArMdJPXjQha5RdeWlLh8i3rQrAPjihDg7d3PbmcvU/MiPnz8JKCW/kQT/sZKGd4IFfV0ah1BWo7dpAC/rXmPkTYTd3RXkDr1N+X2emo11ALTY4IRYxiJis2Ead7uz44DuMU+FvRcTSeATkOfZP4YbWR7VfJ+obuACEyhMzhMTKhPrB6lRjL92nUtW9L09EU8+vUcPHYr7l88wgXtoXKgIt/J9smBcXW/pR0v9ajib+Ikb7yiBcikUn7Ne+A
X-MS-Exchange-AntiSpam-MessageData:
	SvFhUbHWkJW4w+Ti+wp3gxEoX4HPJ5Tnggk1bQm3tkAAouuX+vJZR2ApyoDaUJ/JmrUK6CsndL0yTUu9rCGEwMz0DSzLPX1P+P1fgvXHHMPB6rVtRxUuaCeC1aK0cfsfluHwsmfkqD9W4DHuRR5kyD2TK7rFKnUWalna/gKYjyNU2VTHva1yzZiPLCLsmEfdcbcs0gXngvfAs8BZ6SUGaw==
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 5f7f3073-b2c8-47eb-c782-08d8c6c4fb48
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 01 Feb 2021 15:21:01.5899
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-AuthSource:
	HE1EUR04FT014.eop-eur04.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg:
	00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1EUR04HT237
Subject: Re: [PHP-DEV] [RFC] Enumerations, Round 2
From: bobwei9@hotmail.com (Bob Weinand)

--Apple-Mail=_13145F0C-430A-49F5-A6B3-8AA7169527FC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> Am 29.01.2021 um 18:15 schrieb Larry Garfield =
<larry@garfieldtech.com>:=1F=1F=1F=1F=1F=1F=1F=1F=1F=1F=1F=1F=1D=08=1F=1F=1E=

>=20
> And we're back again.  The RFC has been updated with a steady stream =
of smaller improvements based on feedback and testing, and is now in its =
Final Form(tm) (we think).  The only major change worth noting is that =
we renamed things. :-)
>=20
> An enum with no scalar backing is now called a Pure Enum, made up of =
Pure Cases.  One that does have backing values is called a Backed Enum, =
made up of Backed Cases.  That change is mainly to allow for future =
expansion to non-scalar backing static values, should the use case =
arise.  Reflection was also reworked a bit to make it more logical.
>=20
> https://wiki.php.net/rfc/enumerations =
<https://wiki.php.net/rfc/enumerations>
>=20
> At this point, Ilija and I consider the RFC done and ready for a vote. =
 Baring any major issues being brought up, we plan to start the vote in =
the first half of next week, probably Tuesday-ish.  If you have any =
other bug reports or tweaks, please speak now or forever hold your =
patches.

Hey,

There is a single point in the RFC which is unreasonable to me, which is =
barring static properties.
I do not consider static properties to be handled the same than normal =
properties. It's perfectly reasonable to prevent normal instance =
properties if we want [pure] enums to be stateless (which makes sense).
It however does not make sense to arbitrarily restrict static =
properties. In the end a static property (on final classes at least) is =
mostly a nice way to express global state, which could be written =
"global $my_namespaced_enum_class_prop_name;" and used then. It's just =
that self::$prop_name is much more readable and user-friendly, including =
for types and static analysis.

I also agree with Nikitas note that IterableEnum is really a suboptimal =
name. If you want to highlight finiteness, maybe call it FiniteEnum. =
UnitEnum would be fine too.

Thanks,
Bob

> --Larry Garfield
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php =
<https://www.php.net/unsub.php>

--Apple-Mail=_13145F0C-430A-49F5-A6B3-8AA7169527FC--