Re: Re: [RFC] PHP Namespace Policy
| From: | Michael Morris | Date: | Fri, 24 Apr 2020 23:14:13 +0000 |
| Subject: | Re: Re: [RFC] PHP Namespace Policy | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-109838@lists.php.net to get a copy of this message | ||
On Fri, Apr 24, 2020 at 6:09 PM Mark Randall <marandall@php.net> wrote:
> On 25/04/2020 00:00, Michael Morris wrote:
> > So, in steps:
> >
> > 1. Take the current function roster - all of it - and put it in
> > \PHP\Legacy\. So the formal name of strpos would become
> > \PHP\Legacy\strpos.
> > 2. The root namespace would be empty BUT...
> > 3. An INI directive set globally or per directory can set which namespace
> > is bound to root. Initially this would be "\PHP\Legacy", so all legacy
> > code would not have to change - it would run in the new version and find
> > all of its functionality without incident. This is critical - as this
> > directive would likely need to stay as is for two majors minimum,
> possibly
> > more.
>
> Thank you for the contribution.
>
> However, such a change would never, ever be accepted. With good reason.
>
> Mark Randall
> marandall@php.net
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
What good reason? Because it is hard?