You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that this tool should be able to work with source codes or even with source files directly.
For example, in the current implementation of the checker module in py2eo, to use the astranaut, I use our custom python parser, convert from our tree to the astranaut tree, run the TreeTransformer, then convert the tree back to our view and use our printer. But in this situation, I don't need the tree at all, I only need the input file to be mutated by the rule I'm passing in.
It seems that the lack of parsing and printing codes greatly reduces the versatility of the tool, because the user needs to parse and print for each grammar again.
Do you think it is appropriate to build in this tool support for interacting with source codes for this grammar (for example, in the same format as antlr accepts)?
The text was updated successfully, but these errors were encountered:
It seems that this tool should be able to work with source codes or even with source files directly.
For example, in the current implementation of the checker module in py2eo, to use the astranaut, I use our custom python parser, convert from our tree to the astranaut tree, run the TreeTransformer, then convert the tree back to our view and use our printer. But in this situation, I don't need the tree at all, I only need the input file to be mutated by the rule I'm passing in.
It seems that the lack of parsing and printing codes greatly reduces the versatility of the tool, because the user needs to parse and print for each grammar again.
Do you think it is appropriate to build in this tool support for interacting with source codes for this grammar (for example, in the same format as antlr accepts)?
The text was updated successfully, but these errors were encountered: