Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:112429
To: internals@lists.php.net
References: <d1c4689e-9120-4e90-837c-a1b3eac63cd6@www.fastmail.com>
 <CA46B60F-AF67-4706-8D66-E14A64739A99@mabe.berlin>
 <f58c2a28-d603-4eb7-8fe5-aa5cfec47382@www.fastmail.com>
Message-ID: <d03c5f1d-b544-c747-34e5-69f344cf0707@gmail.com>
Date: Sat, 5 Dec 2020 15:47:07 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.5.1
MIME-Version: 1.0
In-Reply-To: <f58c2a28-d603-4eb7-8fe5-aa5cfec47382@www.fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] [RFC] Enumerations
From: rowan.collins@gmail.com (Rowan Tommins)

On 05/12/2020 15:08, Larry Garfield wrote:
>> * Are cases serializable?
>>    `Suit::Spades === unserialize(serialize(Suit::Spades)) // true`
> Right now they'd do the same as objects, so they'd serialize as an object.  Unserializing like that, though... hm, that would probably NOT still be === due to the way PHP handles objects.  That's probably undesireable, but I'm not sure at the moment the best way around that.  I'll have to discuss with Iliya.
>

I guess what it comes down to is whether / how easily a class can return 
an existing instance when asked to unserialize, rather than setting 
properties on an existing instance. That is, given the string 
"C:4:Suit:6:{Spades}" can the class definition return the appropriate 
singleton for Suits::Spades rather than a newly constructed object?

If this proves tricky to implement, it would probably be better to 
forbid serialization than using the default object format and breaking 
the singleton-ness of the case objects.


Regards,

-- 
Rowan Tommins (né Collins)
[IMSoP]