I don't understand this 100% but it sounds awesome. +1
On Sun, Jul 15, 2012 at 12:14 PM, Michael Morris <[email protected]>wrote:
> When Adobe moved from Actionscript 2 to Actionscript 3 they placed all
> existing functions into a legacy namespace. Similarly, I believe that
> may be PHP's best shot for smoothing out the API.
>
> 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.
>
> On Sat, Jul 14, 2012 at 11:49 PM, Morgan L. Owens <[email protected]>
> wrote:
> > On 2012-07-14 04:12, jpauli wrote:
> >>
> >> On Fri, Jul 13, 2012 at 5:33 PM, Anthony Ferrara <[email protected]>
> >> wrote:
> >>>
> >>>
> >>> 4. Rewrite the entire parser completely. I keep hearing about how bad
> >>> PHP's
> >>> parser is, and how it's growing out of control. Perhaps this is a good
> >>> time
> >>> to rewrite it (perhaps changing semantics slightly) to be better
> adapted
> >>> towards future changes...
> >>
> >>
> >> We have an RFC and a patch playing with lemon parser. Actually, just a
> >> conversion, reentrant.
> >> Refer to Pierrick or Felipe about it :-)
> >>
> > Will the conversion include writing a formal definition of the language
> from
> > the perspective of someone planning to write a PHP parser? Right now the
> > only way to get such a definition is to reverse-engineer the Bison
> source.
> >
> >
> >
> > --
> > PHP Internals - PHP Runtime Development Mailing List
> > To unsubscribe, visit: http://www.php.net/unsub.php
> >
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
*Brandon Wamboldt*
Programmer / Web Developer
StackOverflow Careers
Profile<http://careers.stackoverflow.com/brandonwamboldt>-
GitHub
Profile <https://github.com/brandonwamboldt>
-
LinkedIn<https://github.com/brandonwamboldt>
-
My Blog <http://brandonwamboldt.ca/>