meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
technical_support [2020/09/28 19:07] – revuskytechnical_support [2023/05/06 17:23] (current) – revusky
Line 1: Line 1:
 ====== Technical Support ====== ====== Technical Support ======
  
-Our policy is that we only provide technical support for the //latest// version of the tool. That is the version that you can download at [[https://javacc.com/download/javacc-full.jar]]. +Our policy is that we only provide technical support for the //latest// version of the tool. That is the version that you can download at [[https://parsers.org/download/congocc.jar]]. 
  
 Alternatively, your own build is fine //as long as it is built from the latest version of the code//, e.g. your jarfile is the result of: Alternatively, your own build is fine //as long as it is built from the latest version of the code//, e.g. your jarfile is the result of:
  
 <code> <code>
-      git clone https://github.com/javacc21/javacc21.git +      git clone https://github.com/congo-cc/congo-parser-generator.git congo 
-      cd javacc21 +      cd congo 
-      ant full-jar+      ant jar
 </code>    </code>   
  
Line 15: Line 15:
 The point is that there is no support for older versions. This project simply has no concept of a stable version vs. a development version or any of that. The point is that there is no support for older versions. This project simply has no concept of a stable version vs. a development version or any of that.
  
-There is also a strong expectation (though it's not an absolute requirement) that if you want technical support, you will make a good faith effort to use the latest JavaCC 21 features and syntax in your grammars. That is because this is how new features get battle tested in the real world. (//Duh...//) +There is also a strong expectation (though it's not an absolute requirement) that if you want technical support, you will make a good faith effort to use the latest CongoCC features and syntax in your grammars. That is because this is how new features get battle tested in the real world. (//Duh...//) 
  
 In our view, this should not be considered onerous because, in the cases where you have a choice of expressing whatever construct in your grammar using legacy syntax, or using the newer features, you will pretty much invariably be better off using the newer features. So, using the latest feature set is helpful to us, and you will be better off also. (//In other words, it is win-win!//) In our view, this should not be considered onerous because, in the cases where you have a choice of expressing whatever construct in your grammar using legacy syntax, or using the newer features, you will pretty much invariably be better off using the newer features. So, using the latest feature set is helpful to us, and you will be better off also. (//In other words, it is win-win!//)
  
-The preferred way to ask any question is via the forum at https://parsers.org/ or you can open an issue at https://github.com/javacc21/javacc21 +The preferred way to ask any question is via the forum at https://discuss.congocc.org/ or you can open an issue at https://github.com/congo-cc/congo-parser-generator