# Resource to Object conversion

- Thread: https://externals.io/message/111297
- Original archive: https://news-web.php.net/php.internals/111297
- Started by Sara Golemon on 2020-08-03T15:01:30+00:00
- Messages: 2
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · RFCs at https://externals.io/rfc.md · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #111297 — Sara Golemon — 2020-08-03T15:01:30+00:00

URL: https://externals.io/message/111297#111297

I just learned about https://github.com/php/php-tasks/issues/6

Is it the case that we've agreed as a whole to simply make these
conversions (as quiet under-the-hood, should only break `is_resource()` type
of changes) without need for individual RFCs? Or is a perfunctory RFC and
vote called for on each conversion?

-Sara

---

## #111298 — Nikita Popov — 2020-08-03T15:09:22+00:00

URL: https://externals.io/message/111297#111298 · In reply to: #111297

> I just learned about https://github.com/php/php-tasks/issues/6
>
> Is it the case that we've agreed as a whole to simply make these
> conversions (as quiet under-the-hood, should only break `is_resource()` type
> of changes) without need for individual RFCs? Or is a perfunctory RFC and
> vote called for on each conversion?
>

Right, these conversions to "opaque" objects are primarily internal
representation changes that do not affect the API of the extension, modulo
 `is_resource()` checks. In the future, we may wish to add proper
object-oriented APIs to these objects (they are currently maximally locked
down to allow future extension). Those API additions should go through the
RFC process (or at least mailing list discussions) as they tend to be more
nuanced than dumb resource->object conversions.

Nikita
