Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "XQuery Development Tools/Extension points"
(Describe tokenizer extension point.) |
(Add parser extension point definition) |
||
| Line 5: | Line 5: | ||
XQDT provides a tokenizer and an ad-hoc incremental parser for the XQuery family languages standardized (or being standardized) by the W3C. Vendors-specific language extension can be achieved by providing vendor-specific lexer and parser, using the following extension points: | XQDT provides a tokenizer and an ad-hoc incremental parser for the XQuery family languages standardized (or being standardized) by the W3C. Vendors-specific language extension can be achieved by providing vendor-specific lexer and parser, using the following extension points: | ||
| − | - org.eclipse.wst.xquery.sse.core.tokenizer: XQuery tokenizer. Must implement ITokenizer. XQDT tokenizer is based on [http://jflex.de/ JFlex]. Since JFlex does not come with a extension mechanism, one solution is for each vendor to change directly the base tokenizer and to manually patch any changes. | + | - org.eclipse.wst.xquery.sse.core.tokenizer: XQuery tokenizer. Must implement ITokenizer. XQDT tokenizer is based on [http://jflex.de/ JFlex]. Since JFlex does not come with a extension mechanism, one solution is for each vendor to change directly the base tokenizer and to manually patch any changes. |
| − | - | + | - org.eclipse.wst.xquery.sse.core.modelBuilder: incremental XQuery parser responsible for updating the model (AST). |
Latest revision as of 11:37, 16 July 2010
This page describes XQDT extension points.
Customizing lexer and parser
XQDT provides a tokenizer and an ad-hoc incremental parser for the XQuery family languages standardized (or being standardized) by the W3C. Vendors-specific language extension can be achieved by providing vendor-specific lexer and parser, using the following extension points:
- org.eclipse.wst.xquery.sse.core.tokenizer: XQuery tokenizer. Must implement ITokenizer. XQDT tokenizer is based on JFlex. Since JFlex does not come with a extension mechanism, one solution is for each vendor to change directly the base tokenizer and to manually patch any changes.
- org.eclipse.wst.xquery.sse.core.modelBuilder: incremental XQuery parser responsible for updating the model (AST).