Re: Feedback on state of some PHP extensions, functions, etc.
| From: | Bishop Bettini | Date: | Wed, 12 Jun 2019 16:16:22 +0000 |
| Subject: | Re: Feedback on state of some PHP extensions, functions, etc. | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-105882@lists.php.net to get a copy of this message | ||
On Wed, Jun 12, 2019 at 11:35 AM G. P. B. <george.banyard@gmail.com> wrote:
> - PharData::setAlias, PharData::setDefaultStub and PharData::setStub
> always throw PharException
>
> <https://www.php.net/manual/en/class.pharexception.php> [11]
> [12] [13]
> [11] https://www.php.net/manual/en/phardata.setalias.php
> [12] https://www.php.net/manual/en/phardata.setdefaultstub.php
> [13] https://www.php.net/manual/en/phardata.setstub.php
I don't know how much this is used in the wild, but these methods exist so
that a user may treat a Phar and a PharData as interface-equivalent objects
independent of the phar.readonly INI setting. I lean toward leaving these
no-op methods as is, but I am happy to further discuss their merit.