Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update reference manual: add specification querying API #20

Open
GoogleCodeExporter opened this issue Mar 14, 2015 · 1 comment
Open

Comments

@GoogleCodeExporter
Copy link
Contributor

The specification querying API introduced by fixing issue #17 and issue #19 still
has to be documented in the online documentation.

Original issue reported on code.google.com by Christoff.Buerger on 18 Jun 2013 at 12:22

@GoogleCodeExporter
Copy link
Contributor Author

To document the specification querying API (RACR reflection) is postponed until
the RACR meta-language is stable.

Explanation of RACR meta-language: RACR is currently implemented in itself.
This means, that a RACR language is given to specify the RACR specification
language. In consequence, specifications are just ASTs of this meta-language,
such that AST rules, productions, symbols, attributes and respective analyses
on specifications are AST nodes and attributes of the RACR meta-language. The
meta-language can be queried using RACR's query API (ast-child, att-value
etc.), such that no special specification querying API is necessary.
Nevertheless, the meta-language still has to be documented.

Original comment by Christoff.Buerger on 13 Mar 2015 at 1:53

@christoff-buerger christoff-buerger changed the title Update reference manual: Add specification querying API update reference manual: Add specification querying API Oct 14, 2017
@christoff-buerger christoff-buerger changed the title update reference manual: Add specification querying API update reference manual: add specification querying API Oct 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants