The following is a short and drafted schedule for the POOL project, it doesn’t contain any dates and should only give an idea, what I’m going to do next in the project and what I’ve already done.
Almost done
Create a draft of the syntax (I’ve to admit that I’m currently working on the class syntax and on the variable container syntax)
TODO
Publish the draft
Figure out the core libraries (like System, etc.)
Parser grammar, which produces the AST
Tree filters to optimize and annotate the AST (convert for example 2+3 to 5)
Tree based interpreter
Objects, scope, functions, etc.
Tree based interpretation
Optimization of the interpreter
More built in libraries
Language manual with lot’s of example code and a website as I think the project will (after creating a tree based interpreter) more than half a year old.
Johannes Bechberger is a JVM developer working on profilers and their underlying technology in the SapMachine team at SAP. This includes improvements to async-profiler and its ecosystem, a website to view the different JFR event types, and improvements to the FirefoxProfiler, making it usable in the Java world. His work today comprises many open-source contributions and his blog, where he regularly writes on in-depth profiling and debugging topics. He also works on hello-ebpf, the first eBPF library for Java. His most recent contribution is the new CPU Time Profiler in JDK 25.
New posts like these come out at least every two weeks, to get notified about new posts, follow me on BlueSky, Twitter, Mastodon, or LinkedIn, or join the newsletter:
