Quick Links to Turorials and Docs
We want to create Parsing API to:
- Unify registration of parsers
- Allow language embedding
- Allow file indexing
- Unify threading, starting/canceling parser tasks
- Avoid code duplication
- Simplify implementation of language supports
|Ada||Done, bugfixing. (contrib)|
|EJS||Not planned for 6.7 (contrib)|
|Erlang||Rewrite done (?) -- Status|
|Fortress||Not planned for 6.7 (contrib)|
|Scala||Done, bugfixing. (contrib)|
|Tcl/Tk||Not planned for 6.7 (contrib)|
We have experience with Retouche, GSF and Schliemann and we want to make an API, which will rise from our experience with those frameworks. The API is not intend to be revolutionary. It is evolutionary development.
The API will have several parts:
- Defines registration of parsers
- Defines threading
- Concept of Virtual Source (support for language embedding)
- No support for phases
- No ordering of parsers
- Provides scanning infrastructure
- Allows registration of Index providers
- RepositoryUpdater - listening on file and document changes
- "Generic ClassPath"
- Provides something like ClassPath to specify source roots (folders, archives)
- UserAction & Modification tasks
- Change represented by ModificationResult (in fact textual diff)
- Need source position translators for embedded languages
API must be well documented. Developer documentation is a must.
- Unit testing.
- Functional testing through language support modules.
- Well defined threading and starting/canceling parser tasks could improve performance of code completion and features in various Editors
- Startup scanning will be slower because of scanning and indexing not only Java, but possibly all files
We have been tracking all tasks related to Parsing API in IssueZilla under Editor / Parsing & Indexing category. Please use the following query to see all unresolved issues sorted by their priority.