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

Feature/Bug: Disable cache for Parse Tree #264

Open
lublak opened this issue Apr 22, 2024 · 8 comments
Open

Feature/Bug: Disable cache for Parse Tree #264

lublak opened this issue Apr 22, 2024 · 8 comments
Labels
possible bug Could be a bug

Comments

@lublak
Copy link
Contributor

lublak commented Apr 22, 2024

I sometimes have the problem that the Prae Tree does not update. I have adjusted the rules but the parse tree does not update after "F5". Only a complete restart of vscode solves the problem. Is a cache to blame here? And would it be possible to simply have an option to deactivate it?

@lublak
Copy link
Contributor Author

lublak commented Apr 22, 2024

Another thing: apparently the parse tree is already updating itself. But not the rules behind it. So as soon as I change the input file, the tree updates. but based on the opened grammar file. If I change the grammar file, it does not update. Even if I then change the input file, it still adopts the state from before the change in the Grammar file.

@lublak
Copy link
Contributor Author

lublak commented Apr 22, 2024

Example, bevor change:

grafik
grafik

Example, after change:

grafik
grafik

Example, after restarting vscode:

grafik

@mike-lischke
Copy link
Owner

mike-lischke commented Apr 22, 2024

I assume that after you change the grammar, you save it and start the debugging process again. You didn't mention these essential things, so I better ask.

@lublak
Copy link
Contributor Author

lublak commented Apr 22, 2024

@mike-lischke Oh, right! Sorry that I gave you this information directly. But yes, I'll start the debugging process again.

@lublak
Copy link
Contributor Author

lublak commented Apr 22, 2024

For further information, the other graphs are up to date:
ATN Graph
Railroad
Call Graph

@lublak
Copy link
Contributor Author

lublak commented Apr 22, 2024

More information:
Breakpoints are also not working at all for me at the moment. I hardly use them personally, but maybe it will help with the problem here. I leave nothing untried!

@lublak
Copy link
Contributor Author

lublak commented Apr 25, 2024

I don't know if it might be due to a vscode update. But since I reported it here, it's just that the parse tree only updates if you restart vscode completely. (Version 1.88.1, system setup)

@mike-lischke
Copy link
Owner

Everything indicates that the internal grammar representation (ATN etc.) is not up to date. Needs investigation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
possible bug Could be a bug
Projects
None yet
Development

No branches or pull requests

2 participants