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
As I pointed out here, the "antlr4" tool is not reliable if one tries to just use the "latest" version of Antlr, i.e., don't use the -v option to say what version you want. It looks like the query times out and then the code crashes. This is catastrophic for testing. And, programming around this by detecting this particular crash, as opposed to a legitimate problem with the grammar you are trying to run the tool on, would not be very nice looking scripting code. Already these Bash scripts look like a mess.
We'll need to set the version explicitly for the Go (and likely Cpp) target.
The text was updated successfully, but these errors were encountered:
* Fix for #3514
This change brings back the explicit version tags for Antlr to Cpp and Go targets, avoiding the problem with the "antlr4" Python script.
* Fix the Pwsh version for the Go template.
As I pointed out here, the "antlr4" tool is not reliable if one tries to just use the "latest" version of Antlr, i.e., don't use the
-v
option to say what version you want. It looks like the query times out and then the code crashes. This is catastrophic for testing. And, programming around this by detecting this particular crash, as opposed to a legitimate problem with the grammar you are trying to run the tool on, would not be very nice looking scripting code. Already these Bash scripts look like a mess.We'll need to set the version explicitly for the Go (and likely Cpp) target.
The text was updated successfully, but these errors were encountered: