Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124937
To: PHP internals <internals@lists.php.net>
Subject: [PHP-DEV] Should there be a `get_declared_enums()` function ?
Message-ID: <66BD5F05.8010409@adviesenzo.nl>
Date: Thu, 15 Aug 2024 03:51:01 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="------------020502060000080606000401"
From: php-internals_nospam@adviesenzo.nl (Juliette Reinders Folmer)

This is a multi-part message in MIME format.
--------------020502060000080606000401
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

L.S.,

I just noticed the following, which struck me as weird/inconsistent:

There are four different OO structures in PHP:
1. Classes
2. Interfaces
3. Traits
4. Enums

For all four, an `*_exists()` function is available, i.e. 
`class_exists()`, `interface_exists()`, `trait_exists()` and 
`enum_exists()` [2].

But only for three out of the four, a `get_declared_*()` function exists.
There is `get_declared_classes()`, `get_declared_interfaces()`, 
`get_declared_traits()`, but no `get_declared_enums()` [2].

I'm aware that enums are internally considered classes and that 
`get_declared_classes()` will retrieve them [1], but the same could be 
said about interfaces and traits, yet they do have their own 
`get_declared_*()` function.

Should a `get_declared_enums()` function be added ?
And should the `get_declared_classes()` function be adjusted to exclude 
enums ?

I did check the enum RFC [3], but I couldn't find any mention or 
discussion about this in the RFC.

Smile,
Juliette


1: https://3v4l.org/0ub6I
2: https://www.php.net/manual/en/ref.classobj.php
3: https://wiki.php.net/rfc/enumerations


--------------020502060000080606000401
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font size="-1"><font face="Verdana">L.S.,<br>
        <br>
        I just noticed the following, which struck me as weird/inconsistent:<br>
        <br>
        There are four different OO structures in PHP:<br>
        1. Classes<br>
        2. Interfaces<br>
        3. Traits<br>
        4. Enums<br>
        <br>
        For all four, an `*_exists()` function is available, i.e.
        `class_exists()`, `interface_exists()`, `trait_exists()` and
        `enum_exists()` [2].<br>
        <br>
        But only for three out of the four, a `get_declared_*()`
        function exists.<br>
        There is `get_declared_classes()`, `get_declared_interfaces()`,
        `get_declared_traits()`, but no `get_declared_enums()` [2].<br>
        <br>
        I'm aware that enums are internally considered classes and that
        `get_declared_classes()` will retrieve them [1], but the same
        could be said about interfaces and traits, yet they do have
        their own `get_declared_*()` function.<br>
        <br>
        Should a `</font></font><font size="-1"><font face="Verdana"><font
          size="-1"><font face="Verdana">get_declared_enums()</font></font>`
        function be added ?<br>
        And should the `get_declared_classes()` function be adjusted to
        exclude enums ?<br>
        <br>
        I did check the enum RFC [3], but I couldn't find any mention or
        discussion about this in the RFC.<br>
        <br>
        Smile,<br>
        Juliette<br>
        <br>
        <br>
        1: <a class="moz-txt-link-freetext" href="https://3v4l.org/0ub6I">https://3v4l.org/0ub6I</a><br>
        2: <a class="moz-txt-link-freetext" href="https://www.php.net/manual/en/ref.classobj.php">https://www.php.net/manual/en/ref.classobj.php</a><br>
        3: <a class="moz-txt-link-freetext" href="https://wiki.php.net/rfc/enumerations">https://wiki.php.net/rfc/enumerations</a><br>
        <br>
      </font></font>
  </body>
</html>

--------------020502060000080606000401--