Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:114864
MIME-Version: 1.0
References: <CAF+90c_2TTC=MiZmmAeUC52iiLU8L3cvvyuZoTwamP5VU79uBQ@mail.gmail.com>
In-Reply-To: <CAF+90c_2TTC=MiZmmAeUC52iiLU8L3cvvyuZoTwamP5VU79uBQ@mail.gmail.com>
Date: Mon, 14 Jun 2021 16:42:40 +0200
Message-ID: <CADyq6s+rbu8-Db6oZd93cUV4KQpeyXdsSB2Z26KHd8hxS9MXqA@mail.gmail.com>
To: Nikita Popov <nikita.ppv@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000004a1d6105c4badfb4"
Subject: Re: [PHP-DEV] Allow objects in define()
From: ocramius@gmail.com (Marco Pivetta)

--0000000000004a1d6105c4badfb4
Content-Type: text/plain; charset="UTF-8"

Hey NikiC,

On Mon, Jun 14, 2021, 16:35 Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals,
>
> With the introduction of enums, it's now possible for constants to hold
> objects. However, this works only when using the `const X = Y` syntax, not
> when using `define('X', Y)`, which still excludes objects.
>
> I've submitted https://github.com/php/php-src/pull/7149 to relax the
> restriction. This means that define() would accept everything apart from
> recursive arrays.
>
> An alternative here would be to allow define() to only accept enum objects
> in particular, but not other objects. I would prefer not to do that, as
> such a restriction would be rather arbitrary, now that the technical work
> to support objects has been done. (PS: Please keep the difference between
> mutability and interior mutability in mind.)
>

I rarely encounter any code using `define()` for anything more than
extremely minimal environment details these days, and even then, it usually
leads to loading an immutable `Environment` object that is then passed
through dependency injection (container or not) to runtime services.

What are the possible use-cases for this, besides enumeration types?

>

--0000000000004a1d6105c4badfb4--