This is an excellent idea. Full BC yet without legacy cruft. Old code runs on legacy support extensions, new code doesn't need it. On Jul 17, 2012 1:51 PM, "Leigh" <lei...@gmail.com> wrote:
> > Basically, the current function library is moved to the legacy > > namespace. The default setting is import the functions of the legacy > > namespace into the root namespace for BC. But with that setting > > turned off all the existing functions go away to be replaced with a > > designed API, instead of a grown one, correcting the mistakes that > > have accumulated over the years. > > Is there any reason why this cannot / should not be implemented as a > PHP 5 compatibility extension? > > I think those who never want to use it (PHP 6 purists) shouldn't have > to have their binaries bloated by legacy code. It would also mean that > the legacy implementation can be developed away from the new core, and > not have any (negative) influence on it. > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
