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
I believe all of our non-antlr dependencies are obtained via submodules. Antlr, on the other hand, is downloaded from github via custom cmake. I think the reasoning behind this discrepancy is that these are the instructions suggested by Antlr itself. Or perhaps it is that Antlr requires java?
Part of me thinks that having these things be consistent will make it easier to understand and maintain for future developers. Is there any particular reason we can't have it as a submodule?
The text was updated successfully, but these errors were encountered:
Part of the reasoning is the Java dependency. You don't need to pull in a Java compiler to use the prebuilt JAR tool (just the JRE). (For reference, the tool is what converts the grammar into C++ code. There's also the C++ runtime which does the evaluation at runtime.). As a C++ developer having to install a Java compiler to build a C++ library is a bit of a stretch.
That said it will work as a submodule and we can certainly try it. Now that we have a version in it'll be easier to compare what happens with a PR.
I believe all of our non-antlr dependencies are obtained via submodules. Antlr, on the other hand, is downloaded from github via custom cmake. I think the reasoning behind this discrepancy is that these are the instructions suggested by Antlr itself. Or perhaps it is that Antlr requires java?
Part of me thinks that having these things be consistent will make it easier to understand and maintain for future developers. Is there any particular reason we can't have it as a submodule?
The text was updated successfully, but these errors were encountered: