Activity
From 06/04/2026 to 07/03/2026
07/03/2026
- 01:56 PM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I have some good news to share! One of the larger applications successfully passed the first phase of the conversion,...
07/02/2026
- 09:35 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- During today's meeting, we decided to keep the changes in the @oo@ package since the @skeleton@ project is difficult ...
- 07:48 AM Feature #7178: move the buffer scoping calculations to parse time
- > I can still integrate tests from #4105, #4121, #4207, #4208, #4231 (double check), #4440, #4492, #4782, #4791, #665...
- 06:41 AM Feature #7178: move the buffer scoping calculations to parse time
- Second round.
I did not find any tests for #4123, #4124, #4147, #4160, #4162, #4170, #4171, #4174, #4181, #4182, #...
07/01/2026
- 09:47 AM Feature #7178: move the buffer scoping calculations to parse time
- > Greg, I think there's a good reason to go into the related tasks for all those tasks and check if we can find more ...
- 09:41 AM Feature #7178: move the buffer scoping calculations to parse time
- Amazing!
I did not find any tests for #1521, #1868, #1896, #1969, #2683, #3024, #3253, #3255, #3310, #3471, #3490,... - 05:20 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- It looks like the test case above isn't compiling in OE and requires a @SUPER()@ call to be correct. Consequently, I ...
06/30/2026
- 10:23 AM Feature #7178: move the buffer scoping calculations to parse time
- In the latest standard workstation, I've added a tool called @bzr-issues@ which can be used to build a list of all ta...
06/29/2026
- 03:15 PM Feature #1757: update ANTLR to latest version
- A wiki page with guidance on how we migrate from ANTLR2 to ANTLR4 is in [[p2j:ANTLR Migration Guide]].
06/24/2026
- 10:06 AM Feature #6320: sharded schemata
- Yes, using a per-module namespace would be a way to solve the issue I noted in #6320-5.
- 10:03 AM Feature #6320: sharded schemata
- Greg Shah wrote:
> > This means that apps/modules need to be able to be converted in pieces and executed at runtime ... - 07:08 AM Feature #7178: move the buffer scoping calculations to parse time
- I've wrapped up the FOR EACH WHERE/BY, dataset with relation-fields, lots of unqualified fields/tables tests.
I'm ...
06/23/2026
- 03:53 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Constantin, have you had a chance to look at the approach mentioned above? Let me know what you think.
06/22/2026
- 07:11 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I've committed the build changes as rev *16622*. @./gradlew all@ should work now.
06/19/2026
- 06:39 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- 10804b was rebased, new rev is *16621*.
- 06:08 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Next, I'll rabase the branch, setup new big application, redo the conversion, and solve the remaining parser issues. ...
- 05:04 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Paula Păstrăguș wrote:
> One testcase is still failing: @AdaptiveQuery.initialize@ now receives @WHOLE-INDEX@ as a p...
06/18/2026
- 08:10 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- *Update*: LATEST Hotel GUI performance comparison between ANTLR2 and ANTLR4. (Please note that all conversions were e...
- 04:38 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- For Hotel GUI, the total time needed to generate the tokens with the ANTLR2 based lexer and convert them to ANTLR4 co...
- 08:02 AM Feature #7178: move the buffer scoping calculations to parse time
- The tests were developed on the examples from #7178-2.
This is a recap of the tests that were completed or have a ...
06/17/2026
- 09:24 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- The approach seems to work! 🥳 I was able to get the same AST for @standard.df@. However, there are still a few remain...
06/16/2026
- 06:43 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I am moving to an alternative approach for the ANTLR4 lexer performance issue (based on the idea mentioned by Greg in...
06/15/2026
- 02:59 PM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I added temporary lexer profiling in order to measure the token generation cost per token type, aggregated across all...
- 12:26 PM Feature #11540: rework conversion back-end to add optional support for output to C#
- This is long awaited feature. The conversion architecture was built with thin in mind. When I first read about it, I ...
- 09:41 AM Feature #11540: rework conversion back-end to add optional support for output to C#
- There are some customers that prefer C# to Java.
The core of both languages have nearly identical syntax and C# ... - 09:21 AM Feature #11540 (New): rework conversion back-end to add optional support for output to C#
06/12/2026
- 08:42 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Before moving forward, another project conversion progressed further than in previous attempts, it reached the *serve...
- 08:35 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Another slowdown source is the @evaluateExpr@ method: under ANTLR2, Hotel GUI spends *5.3 seconds* in it, whereas und...
06/11/2026
- 08:16 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- 10804b is at rev *16584* now (here you can find today's parser improvements).
- 08:03 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I also attached a log file in my previous post. It includes the total time ANTLR4 spends in prediction mode for each ...
- 08:00 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Hmm, for Hotel GUI, @createShadowNodes@ takes around @0.2@ seconds in total, which seems reasonable from my POV. (we ...
- 07:51 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- In this 2X difference for the front end, 40% comes from the ANTLR4 code and 60% from something else. The other major...
- 07:45 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- *Update*: Hotel GUI performance comparison between ANTLR2 and ANTLR4.
|_. Metric |_. ANTLR2 |_. ANTLR4 |
| Total ...
06/10/2026
- 02:35 PM Feature #11528: implement COMPILE stmt
- Although this is a 4GL language statement, possibly best considered part of Base Language, from our perspective it ha...
- 02:22 PM Feature #11528 (New): implement COMPILE stmt
- 10:12 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- 10804b is at rev *16583* now (the latest).
- 10:04 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Greg, it is not 3x slower anymore, it is only around 2x now, and I think I can still push the boundaries:)
- 10:00 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- *Update*: the current Hotel GUI parse time is *49 seconds*. I think I can still improve this further through parser c...
- 09:20 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Right, I remember having this error from the very beginning, basically two years ago:-)
Anyway, I think a fresh ch... - 09:16 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- > It is not valid, a dot is missing here:
Hmmm. Something is wrong here with the project. You are working with H... - 07:11 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Greg Shah wrote:
> ANTLRv2 and ANTLRv4 both have their loops and optional alternatives set to be greedy by default. ... - 07:06 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Paula Păstrăguș wrote:
> Greg Shah wrote:
> > > This suggests that we may also need some special tricks for cases w... - 07:06 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Greg Shah wrote:
> > This suggests that we may also need some special tricks for cases where a @no viable alternativ... - 06:54 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Paula Păstrăguș wrote:
> Another important thing I noticed is that the ANTLR4 prediction algorithm does not seem to ... - 06:49 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- > One bottleneck I identified is the @toolbar.p@ file. It throws an NPE caused by a @no viable alternative@, which is...
- 06:23 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Greg, is a @()*@ construct in ANTLR2 greedy or non-greedy by default? I only found three @options@ blocks with @greed...
- 06:11 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Another important thing I noticed is that the ANTLR4 prediction algorithm does not seem to provide a reliable way to ...
- 05:44 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- *Update*: Hotel GUI parse time has now dropped to *1 minute and 8 seconds*, with a total conversion time of *5 minute...
06/09/2026
- 02:31 PM Feature #10804: create replacement AST implementation for use with ANTLR 4
- > Greg, I remember you suggested something related to this at some point, but I do not recall the exact details. Coul...
- 10:22 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- The lexer doesn't appear to be the bottleneck. Using @tokens.fill()@ and summing the elapsed times across all Hotel_G...
- 09:42 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I think it is time to document some findings and updates here.
At this point, I think I have stabilized the Progre... - 12:48 PM Support #6409: generate "railroad style" syntax diagrams for the progress parser
- h1. Analysis of Approach
h2. Objective
Provide high-quality, readable "railroad" syntax diagrams for the full r...
06/05/2026
- 12:08 PM Feature #6320: sharded schemata
- Using TRPL for import is overkill since the tree structure is so trivial. So, yes, I agree it should move away.
- 11:36 AM Feature #6320: sharded schemata
- Greg Shah wrote:
> If the details are in annotations in the DMOs, do we need the P2O documents? Annotations seems c... - 11:08 AM Feature #6320: sharded schemata
- I think it is best to remove the @.dict@ files too.
- 11:00 AM Feature #6320: sharded schemata
- Greg Shah wrote:
> If the details are in annotations in the DMOs, do we need the P2O documents? Annotations seems c... - 10:54 AM Feature #6320: sharded schemata
- If the details are in annotations in the DMOs, do we need the P2O documents? Annotations seems cleaner.
- 10:53 AM Feature #6320: sharded schemata
- Greg Shah wrote:
> Octavian Adrian Gavril wrote:
> > Understood, that makes perfect sense for production discipline... - 10:37 AM Feature #6320: sharded schemata
- Octavian Adrian Gavril wrote:
> Understood, that makes perfect sense for production discipline. But does this setup ... - 10:12 AM Feature #6320: sharded schemata
- Understood, that makes perfect sense for production discipline. But does this setup still fundamentally confirm the O...
- 09:57 AM Feature #6320: sharded schemata
- At production, the customer will expect a merged database not to run against a shared. This means there is an assump...
- 09:46 AM Feature #6320: sharded schemata
- I did some testing in an OE environment and want to see if I got it right regarding how this feature works.
I set up... - 04:26 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Octavian Adrian Gavril wrote:
> This is the fix:
> [...]
>
> I will include this patch in the next revision of *... - 03:21 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- I found a fix for the issue described in my previous note.
In @annotations/method_defs.rules@, we decide whether t...
06/04/2026
- 09:21 AM Feature #6320 (WIP): sharded schemata
- 09:20 AM Feature #11404 (WIP): Implement annotation-based resolution for database dependencies.
- 08:14 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- I've fixed the regression documented above by skipping collision checks for parent constructor names.
While testin... - 03:16 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Okay, it seems that @calculateUniqueJavaMethodName@ is searching for parent constructors as well. Since I disallowed ...
- 01:54 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Unfortunately, I'm seeing a few new differences, so I might have regressed something regarding constructor names in t...
Also available in: Atom