Re: Reflect.parse (from RE:typeof null)

it appears that the SpiderMonkey AST has emerged as a de-facto standard. Really? I guess there are many more users of Uglify and Esprima is growing fast. Personally I never heard of any non-Mozilla uses of the SpiderMonkey API, but perhaps you can point to some. I was merely stating my persona

Re: Reflect.parse (from RE:typeof null)

On May 10, 2012, at 8:28 AM, Claus Reinke wrote: >>> Will Reflect.parse be standardized? > >> Maybe. It's too late for ES6 and different implementations have different >> concrete parse trees, I bet -- although perhaps they all agree on concrete, >> there's still the question of mapping to abs

Re: Reflect.parse (from RE:typeof null)

On Thu, May 10, 2012 at 8:28 AM, Claus Reinke wrote: >>> Will Reflect.parse be standardized? > > >> Maybe. It's too late for ES6 and different implementations have different >> concrete parse trees, I bet -- although perhaps they all agree on concrete, >> there's still the question of mapping to a

Re: Reflect.parse (from RE:typeof null)

Will Reflect.parse be standardized? Maybe. It's too late for ES6 and different implementations have different concrete parse trees, I bet -- although perhaps they all agree on concrete, there's still the question of mapping to abstract. This needs more time to bake. It's also a mouth to fee

Re: Reflect.parse (from RE:typeof null)

Maybe. It's too late for ES6 and different implementations have different concrete parse trees, I bet -- although perhaps they all agree on concrete, there's still the question of mapping to abstract. This needs more time to bake. It's also a mouth to feed, not as much as a second built-in par

Reflect.parse (from RE:typeof null)

> > The Reflect namespace object is part of direct proxies, also populated in > SpiderMonkey (not web-facing) by Reflect.parse to get an AST for a given > source string. Will Reflect.parse be standardized? kevin ___ es-discuss mailing list es-discuss@m