The following essay outlines the main evolution in the API generated by CongoCC from its origins in the Dark Ages up until now. The Journey of a Thousand Leagues Begins with a Single Step Let’s say you go on an excursion to a national park and there is a well known hiking trail that goes …
Some days ago, I added a new setting. If, at the top of your grammar, you write: TERMINATING_STRING=”some string”; this means that the input you’re parsing is guaranteed to end with that string. If the file ends with that string already, then it does nothing. Otherwise, it tacks that string to the end. In actual …
The TERMINATING_STRING setting, a new (and quite minor!) feature Read More »
(The TLDR: Nested lookahead was always broken in legacy JavaCC. This is finally fully addressed (as of 11/26/2022) in JavaCC 21. However, since this fix has a lot of potential to break existing code, for now, the fix is only in effect if you put LEGACY_GLITCHY_LOOKAHEAD=false at the top of your grammar(s). Meanwhile, you should …
A very annoying detail in computing (annoying in particular because the whole thing seems so utterly pointless) is this whole issue of line endings in text files. In Microsoft Windows, the operating system that dominates the desktop, a line ending is denoted by "carriage return" followed by "line feed", or CR-LF for short. (Namely the …
I recently introduced a couple of "pseudo-annotations" (I’ll explain the pseudo part later) that can be used in code injections to express things in a much more succint manner. Here is an example: INJECT Foo : { @property String name; … } and the code generated in Foo.java corresponding to that line will be: private …
In conjunction with New Year 2021 (a landmark year for JavaCC 21 for sure!) I decided to scratch some longstanding itches — even at the expense of introducing some (minor) backward incompatibilities. The various option settings can only be set in the grammar file. There was a longstanding setup in legacy JavaCC (carried forward in …
Happy New Year! Some Backward-Incompatible API Changes! Read More »