Updates:
Status: Invalid
Comment #1 on issue 2889 by [email protected]: Provide public API for
V8's JavaScript parser
http://code.google.com/p/v8/issues/detail?id=2889
I highly doubt that this will ever happen, for various reasons:
* The fact that we build an AST is an implementation detail, and there
is actually nothing in the JavaScript spec forcing us to actually build it.
* Even if we decided to expose the fact that we build an AST, it would
expose *tons* of details, because our AST nodes contain far more than
syntactic information (that's actually bad, but that's how it is currently).
* The structure of the AST must remain flexible, I don't think we want
to commit us to one form or the other. Exposing the AST in an external API
would imply some kind of commitment to keeping it stable, a burden which we
don't want to take.
* There are a few things planned where the interface above is not
suitable at all, think of e.g. a stream-like interface opening up the
possibility of concurrent/parallel parsing etc.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
