Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125442
Date: Thu, 5 Sep 2024 15:14:46 -0400
To: =?utf-8?Q?Rowan_Tommins_=5BIMSoP=5D?= <imsop.php@rwec.co.uk>
Cc: "=?utf-8?Q?internals=40lists.php.net?=" <internals@lists.php.net>
Message-ID: <5D9EE367-6D93-4E7A-853E-855EE202D8D8@getmailspring.com>
In-Reply-To: <1adfd0cd-416e-44e6-8d4b-7061a31199b0@app.fastmail.com>
References: <1adfd0cd-416e-44e6-8d4b-7061a31199b0@app.fastmail.com>
Subject: Re: [PHP-DEV] RFC: Deprecate json_encode() on classes marked as
 non-serializable
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="66da0326_327b23c6_15a82"
From: john@coggeshall.org (John Coggeshall)

--66da0326_327b23c6_15a82
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

> So if we had a #[NotSerializable] attribute (which I agree might be a good idea) it would be implemented by setting the ZEND_ACC_NOT_SERIALIZABLE flag on a class definition, and if this RFC passes, it would automatically apply to json_encode() as well as serialize().
>

My mistake, I haven't familiarized myself with some of the more recent engine changes but this all makes sense. My point was more to ask the question "Would it be reasonable to expand the scope of this RFC to introduce a #[NotSerializable] attribute along with the rest of the proposal?"
Coogle
--66da0326_327b23c6_15a82
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<blockquote><div><div>So if we had a =23=5BNotSerializable=5D attribute (=
which I agree might be a good idea) it would be implemented by setting th=
e <code>ZEND=5FACC=5FNOT=5FSERIALIZABLE flag on a class definition, and <=
/code>if this R=46C passes, it would automatically apply to json=5Fencode=
() as well as serialize().</div></div></blockquote><br><div>My mistake, I=
 haven't familiarized myself with some of the more recent engine changes =
but this all makes sense. My point was more to ask the question =22Would =
it be reasonable to expand the scope of this R=46C to introduce a =23=5BN=
otSerializable=5D attribute along with the rest of the proposal=3F=22</di=
v><br><div>Coogle</div>
--66da0326_327b23c6_15a82--