XText Workflow for Expensive Analysis [message #1807988] |
Thu, 13 June 2019 18:29 |
Ben Holland Messages: 34 Registered: April 2019 |
Member |
|
|
I have a DSL implementation currently working with code generation, however my DSL contains some properties that I would like to do further analysis of. I think this analysis would be different than the XText validation in that the analysis could be expensive (proving properties about the DSL program) and I would like to trigger it on-demand by the user after code generation is complete. I don't want to trigger this logic every time the code is compiled.
Where would be the right place to put this logic? The analysis would need to consider the AST of the full program.
[Updated on: Thu, 13 June 2019 18:30] Report message to a moderator
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03178 seconds