Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125630
Precedence: bulk
MIME-Version: 1.0
Date: Thu, 19 Sep 2024 14:19:09 +0200
To: John Coggeshall <john@coggeshall.org>
Cc: Philip Hofstetter <phofstetter@sensational.ch>, PHP internals
 <internals@lists.php.net>
Subject: Re: [PHP-DEV] RFC: Deprecate json_encode() on classes marked as
 non-serializable
In-Reply-To: <98553A91-FD3F-4E1B-91D9-D8B00CAD5FC5@getmailspring.com>
References: <CAGKNXQG32aF58gPnf1ywbmde72F_Wwjib0oXhN_ve6336RnQXg@mail.gmail.com>
 <98553A91-FD3F-4E1B-91D9-D8B00CAD5FC5@getmailspring.com>
Message-ID: <b984aa24c4b7893b4fc1e3aad2fe3de9@bastelstu.be>
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

Am 2024-09-05 18:03, schrieb John Coggeshall:
> I would suggest we take a step back from this and look at it with a bit 
> more of a wider lens. It seems to me that this would be a good place to 
> have an attribute (e.g. #[NotSerializable] ) that could be defined for 
> any class (with ZEND_ACC_NOT_SERIALIZABLE being automatically given 
> this attribute)? It just seems to be a more holistic approach that 
> makes sense, rather than basing it on internal engine stuff and/or 
> limiting it to internal objects.

FWIW There already is such an RFC: 
https://wiki.php.net/rfc/not_serializable

Discussion thread is here: https://externals.io/message/121969#121969

Best regards
Tim Düsterhus