Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122139
MIME-Version: 1.0
References: <CAH5C8xW_CqSf1qybs9vG6qyo_1pzvbzkv5bVjUeyKNvAsTBdaw@mail.gmail.com>
 <CAGBsUre-J7atR=-sRM5ycE+S8uFQN452kjcJcoskQQ_NenMrSg@mail.gmail.com>
In-Reply-To: <CAGBsUre-J7atR=-sRM5ycE+S8uFQN452kjcJcoskQQ_NenMrSg@mail.gmail.com>
Date: Tue, 9 Jan 2024 09:08:08 +0100
Message-ID: <CAH5C8xVoqcsVEfNQKvDZVDBiqPMK5TqHaB4Axdni9xHyJ-T0Kw@mail.gmail.com>
To: Kamil Tekiela <tekiela246@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000004394a9060e7ed13f"
Subject: Re: [PHP-DEV] [RFC] [Vote] Resource to object conversion
From: kocsismate90@gmail.com (=?UTF-8?B?TcOhdMOpIEtvY3Npcw==?=)

--0000000000004394a9060e7ed13f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Kamil,

Good question... After the workaround, I think there's less reason to
do the conversion in the next major version indeed. To be honest,
I am not able to recall any use-case where a real BC break could happen.
I mean, there is a very tiny one where resources can be casted to
integers, while objects by default cannot be, but this problem is also
easily solvable (and Nikita had to do it for CurlHandle in the past),
so I don't have any other idea.

In my opinion, the main argument for converting stream resources to objects
in a major version is the "marketing value" of this achievement and possibl=
y
the unintended side-effects/edge cases which we don't yet foresee.

Regards,
M=C3=A1t=C3=A9

--0000000000004394a9060e7ed13f--