-
Notifications
You must be signed in to change notification settings - Fork 22
Generated files are empty #44
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
Comments
Thanks for the report, digging into it. |
Had a further play and I can say that the generation breaks when:
are included, if that helps at all! Seems to not like the time, IP, and anything with double quotes in. (or |
The problem is A silenced execution is a bug of ldetool, where I missed Need to fix it at lexer/grammar level, but this will take a bit of time. |
Makes sense to me, cheers for looking into it so quickly. I'll leave this open just as something to work against for the aforementioned bug(/improvement). |
Need antlr/antlr4#2642 merged |
@naphta seems to be fixed. Not at the level I expected it to be, but I seriously don't want to rely on unmerged functionality. |
Validations are fine from my pov, it's a shame they couldn't be better but certainly the error messages coming out of it would have led me to not raising this issue. Happy to close this off, or leave it open until that antlr PR, up to you. |
Closing it. I have a suspicious I will have a badge "my PR was accepted in ATNTLR in less than five years" LOL. |
My problem is that when I run ldetool the resulting generated go code is an empty file.
Very much in the early stages of playing around (so there may be some glaring mistake), I'm running go 1.16.3 and my lde file is as follows:
and the output from running ldetool is:
The text was updated successfully, but these errors were encountered: