Posts relating to the JavaCC roadmap for future development
When I say "fully supported", I mean all the new features that are categorized as "stable". In fact, the only new language feature that has been promoted to stable in JDK 14 is the new syntax for the Switch statement. This also allows a Switch statement to be used as an expression. In fact, the …
Revisiting LOOKAHEAD Redux Not so long ago, I had a sort of eureka moment when I realized that the legacy LOOKAHEAD construct was fundamentally half-baked or broken. Not only that, but I started narrowing in on how to definitely address the issue! Well, let’s get concrete. Suppose we have a production that looks kind of like this: FooBar : …
New Feature: The =>|| delimiter stands for “scan up to here” Read More »
If you liked LOOKAHEAD, then you’ll love LOOKBEHIND! Actually, I have not added LOOKBEHIND as a new keyword in JavaCC. It is just an informal way of referring to a new feature that I recently added. I implemented this because I realized that there was a very common thing people want to do in a JavaCC grammar …
A few months ago, I started re-examining some of the legacy JavaCC syntax. I realized the pure absurdity of having to write: LOOKAHEAD(Foo() Bar() Baz()) Foo() Bar() Baz() In short order, I allowed people to write the above as: LOOKAHEAD Foo() Bar() Baz() But this started me thinking…. I reasoned that there were doubtless plenty …
Some years back, I was traveling with a couple of Spanish friends, and this was late 2012. We were in Kunming, China and came across a poster that advertised some live music. I was fumbling around for a pen and a bit of paper to jot down the information. I thought to ask my traveling …
It’s Official! The Gigabyte is the new Megabyte! Hurrah! Read More »
A bit over a month ago, I wrote about my intention of tearing out support for “JAVACODE” productions. A JAVACODE production is really just a Java method that is like a pretend grammatical production. I could find very few JavaCC grammars in the wild that used this. I asked whether anybody would miss them and …
One of the very basic goals of this iteration of work on the JavaCC codebase, JavaCC 21, is to turn this into a capable tool for generating fault-tolerant parsers. Traditionally, not just JavaCC, but tools in this space generally, consider that it is their job to parse, i.e. to break down input into its various pieces …
A couple of weeks ago, I implemented a solution to a longstanding Dmitry Dmitriyevich problem with LOOKAHEAD specifications in JavaCC. Dmitry Dmitriyevich (alternatively Ivan Ivanovich or Vladimir Vladimirovich) is my own personal terminology for situations where you are required to write highly repetitive code. (Patriotic Irishmen are welcome to call this the Patrick Fitzpatrick or Gerald …
You know, I bet there are some long-term users of JavaCC who aren’t even aware that JavaCC has this thing called a JAVACODE production. (If you were unaware of this, you weren’t missing much!) Basically, the idea is that you can define something that is, to all intents and purposes, just a plain old java …
About to rip out JAVACODE productions. Does anybody object to this? Read More »
Today, I put in a little incremental effort on the included Java grammar and nailed the last couple of remaining cases that prevented it from parsing all of the java source files in the src.zip included in the JDK 13. There were a few remaining constructs that were still tripping it up and I finally …
Milestone: JavaCC 21 now supports the Java language up to JDK 13 Read More »