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 18:58] – 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, if you are one of the minority of people actually getting their hands dirty in the JavaCC code, then your own build is fine, as long //as you are in synch with the most recent 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 pull +      git clone https://github.com/congo-cc/congo-parser-generator.git congo 
-      ant clean full-jar +      cd congo 
-</code>      +      ant jar 
 +</code>   
  
-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...//) +Of course, the jarfile you get that way will typically be not very different (if at all) from the pre-built one you can directly download. However, in some cases, it will be an even somewhat more advanced version of the code, so obviously, we are interested in any feedback based on that. So that is fine too!
  
-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 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 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 +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!//) 
 + 
 +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