Activity
From 04/14/2026 to 05/13/2026
05/12/2026
- 09:10 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Octavian Adrian Gavril wrote:
> I fixed java constructor names. The remaining differneces are:
> * two mismatched m...
05/11/2026
- 09:46 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Octavian Adrian Gavril wrote:
> I resolved the errors from the @Code Conversion Annotation@ phase. However, new erro... - 07:34 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- I resolved the errors from the @Code Conversion Annotation@ phase. However, new errors related to @OBJECT_INVOCATION@...
05/08/2026
- 09:20 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Unfortunately, during the @Code Conversion Annotation@ phase, I ran into some errors related to inherited class names...
- 08:58 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- I've resolved additional issues in the parsing phase for the other OO application. The parsing phase now passes witho...
05/07/2026
- 09:12 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- To be more specific, I reached a point where the conversion now generates all expected files, including the converted...
- 04:36 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- *Update*: @ant convert@ is now taking around *56* seconds to complete. This means the ANTLR4 based implementation is ...
- 08:32 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- From the OE docs:
> This method supports two overloaded versions. The first version is used to initialize and popu... - 08:16 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Greg Shah wrote:
> What are the signatures of @setParameter()@ in the built-in version and what is the signature in ... - 08:12 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- What are the signatures of @setParameter()@ in the built-in version and what is the signature in the skeleton version?
- 07:46 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- I've noticed some special processing for the @setParameter@ method in @Progress.Lang.ParameterList@. Our built-in ver...
- 06:21 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- > Is there a rule I should follow?
There was no rule. I agree with making it consistent. - 04:33 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- I've updated the casing of the data types in the loaded signatures to match the method call signatures. These changes...
- 03:20 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Is there a convention for the casing of types like @DATASET-HANDLE@ and @TABLE-HANDLE@? I noticed that in @Expression...
05/06/2026
- 06:24 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Octavian Adrian Gavril wrote:
> Aside from the documented differences in #9638-45, I have resolved all other differe...
05/05/2026
- 08:58 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- > Greg, how should we proceed with the remaining items from #9638-45?
Constantin: What do you think? - 08:50 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Aside from the documented differences in #9638-45, I have resolved all other differences. I'm currently focusing on p...
05/04/2026
- 07:06 PM Feature #11437: re-implement call graph hints
- Our current implementation of call graph hints is split into many files (one per program that contains call sites req...
- 06:56 PM Feature #11437 (New): re-implement call graph hints
- 06:56 PM Feature #11436: instrument FWD runtime to generate call graph hints as the converted application ...
- It would be best to finish #11437 before this task.
- 06:48 PM Feature #11436: instrument FWD runtime to generate call graph hints as the converted application ...
- As a converted application executes, we can track every call site and resolved target. This essentially records the ...
- 06:39 PM Feature #11436 (New): instrument FWD runtime to generate call graph hints as the converted applic...
04/30/2026
- 08:53 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- *Update*: The AST produced for the @fwd-embedded-driver.p@ file now has the same structure. Next, I'll also verify th...
04/29/2026
- 08:56 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Another thing. I have such differences:...
- 07:53 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Octavian Adrian Gavril wrote:
> I’ve noticed several other differences in the conversion output. These include incor... - 07:44 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- I’ve noticed several other differences in the conversion output. These include incorrect method selection, missing ob...
- 07:51 AM Feature #10265 (Closed): schema-only conversion
- 06:59 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- *Update*: I compared the ASTs generated by ANTLR2 and ANTLR4 for @fwd-embedded-driver.p@ (full file, without commenti...
04/28/2026
- 12:18 PM Feature #6320: sharded schemata
- +Danut/Alex
- 12:18 PM Feature #6320: sharded schemata
- > This means that apps/modules need to be able to be converted in pieces and executed at runtime as a larger system w...
- 12:06 PM Feature #6256: improved profile support
- See the [[p2j:Chapter_6_Project_Setup|Project Setup]] chapter in the Conversion Handbook.
Also, you can look at th... - 11:51 AM Feature #6256: improved profile support
- I had a project that utilized various zfiles previously now needs to be ported to using profiles. There was a main/de...
- 10:51 AM Feature #6256 (Closed): improved profile support
- 11:39 AM Feature #11423: implement centralized status/error tracking for conversion/dev tools
- h2. Current State
Our current approach to error handling is we write something to STDOUT or a log when a problem i... - 10:55 AM Feature #11423 (New): implement centralized status/error tracking for conversion/dev tools
- 10:44 AM Feature #7180 (Closed): create a centralized manager for the conversion list and per-file/project...
- 10:42 AM Feature #7851 (Closed): automatically add to conversion list all classes referenced via unit test...
- 10:13 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Found a fix for the default constructor names, but I'm still encountering errors with the java names for other method...
- 04:23 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- The testcase project converted successfully without errors. However, I’m now seeing compilation issues in the main bu...
- 10:07 AM Bug #6308: post string literal alternative coding quirk in 4GL preprocessor
- This is the testcase that fails:...
- 06:29 AM Bug #6308: post string literal alternative coding quirk in 4GL preprocessor
- Stefan Vieru wrote:
> Tests that cover this:
> * alternative_coding_quirk_01
> * alternative_coding_quirk_01_analy... - 06:11 AM Bug #6308: post string literal alternative coding quirk in 4GL preprocessor
- Alexandru Lungu wrote:
> Octavian, can you check if there is something left to be fixed here? Just check if the test... - 06:09 AM Bug #6308: post string literal alternative coding quirk in 4GL preprocessor
- Octavian, can you check if there is something left to be fixed here? Just check if the tests here are passing with tr...
04/27/2026
- 10:17 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I managed to get @ant convert@ to run successfully and produce a @.ast@ file. The build now completes, which is a sol...
04/24/2026
- 10:26 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Octavian Adrian Gavril wrote:
> Next, I’m addressing the following warning:
> [...]
>
> This indicates that lega... - 07:35 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Octavian Adrian Gavril wrote:
> I think the problem here is the signature from OO builtin classes. I have identified... - 09:57 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- *Update*: Using *SLL* prediction mode together with @reserved_keywords@ and @unreserved_keywords@, the @fwd-embedded-...
- 08:18 AM Bug #6629 (Test): incremental conversion for OpenClient proxy programs
- Branch 6629a was merged to trunk rev 16536 and archived.
- 07:31 AM Bug #6629 (Merge Pending): incremental conversion for OpenClient proxy programs
- Please merge after 11397a
04/23/2026
- 12:10 PM Feature #11404: Implement annotation-based resolution for database dependencies.
- Ovidiu Maxiniuc wrote:
> I was thinking mostly of 'provided' dmos from a previous iteration of an app-by-app convers... - 10:58 AM Feature #11404: Implement annotation-based resolution for database dependencies.
- I was thinking mostly of 'provided' dmos from a previous iteration of an app-by-app conversion. There are no .ast pro...
- 10:53 AM Feature #11404: Implement annotation-based resolution for database dependencies.
- Ovidiu Maxiniuc wrote:
> This process is similar (if not identical) to that from @MetadataManager.populateFileTable(... - 10:52 AM Feature #11404: Implement annotation-based resolution for database dependencies.
- This process is similar (if not identical) to that from @MetadataManager.populateFileTable()@ which scans the dmo str...
- 09:48 AM Feature #11404: Implement annotation-based resolution for database dependencies.
- This is relatred to app-by-app conversion. Anything related to the lookup or processing of database/temp-tables that...
- 09:45 AM Feature #11404: Implement annotation-based resolution for database dependencies.
- The goal here is to stop relying on the file system for database info during conversion.
This was discovered whil... - 09:37 AM Feature #11404 (WIP): Implement annotation-based resolution for database dependencies.
- 12:08 PM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Paula Păstrăguș wrote:
> I'll try an approach based on a semantic predicate, something like @{ someMethodThatChanges... - 10:25 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I'll try an approach based on a semantic predicate, something like @{ someMethodThatChangesTokenType() }?@. The idea ...
- 08:49 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Octavian Adrian Gavril wrote:
> Greg Shah wrote:
> > > Do you think we should avoid that kind of processing for con... - 06:31 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Octavian Adrian Gavril wrote:
> Octavian Adrian Gavril wrote:
> > Another scenario involves a method call that is n... - 04:15 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Octavian Adrian Gavril wrote:
> Another scenario involves a method call that is not annotated properly because the u... - 02:32 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Greg Shah wrote:
> > Do you think we should avoid that kind of processing for converted java classes?
>
> No, I t...
04/22/2026
- 02:53 PM Support #10231: Document the code style guidelines for ANTLR grammars, based on progress.g
- Some additional rules:
*1.* Do *not* use the shorthand syntax that drops @()@ for subrule processing when there is... - 12:19 PM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Another scenario involves a method call that is not annotated properly because the used parameter is a @TABLE-HANDLE@...
- 10:44 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- Greg Shah wrote:
> > Do you think we should avoid that kind of processing for converted java classes?
>
> No, I t... - 10:39 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- > Do you think we should avoid that kind of processing for converted java classes?
No, I think this is needed for ... - 09:56 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- I've successfully fixed several errors and managed the OO builtin classes to store enough information so that the par...
- 08:37 AM Feature #1757: update ANTLR to latest version
- For further profiling I'll use YourKit profiler.
- 08:35 AM Feature #1757: update ANTLR to latest version
- Paula Păstrăguș wrote:
> Paula Păstrăguș wrote:
> > Tokens generation time: @873586@ ns = 0.000873586 seconds. The ... - 08:31 AM Feature #1757: update ANTLR to latest version
- ...
- 08:20 AM Feature #1757: update ANTLR to latest version
- I only measured @tokens.fill()@, which generates all the tokens.
- 08:18 AM Feature #1757: update ANTLR to latest version
- Make sure this isn't "wall time". The lexer normally only works when asked for tokens. That will be spread over the...
- 08:11 AM Feature #1757: update ANTLR to latest version
- Paula Păstrăguș wrote:
> Tokens generation time: @873586@ ns = 0.000873586 seconds. The lexer is clearly not the iss... - 08:07 AM Feature #1757: update ANTLR to latest version
- Paula, do you profile the actual read from disk? I am aware that ANTLR has a token stream that can be set-up from dis...
- 08:03 AM Feature #1757: update ANTLR to latest version
- I did some searching to see if there was a parser generator that implements true @LL(k)@ but also has its own equival...
- 07:59 AM Feature #1757: update ANTLR to latest version
- Tokens generation time: @873586@ ns = 0.000873586 seconds. The lexer is clearly not the issue.
- 07:53 AM Feature #1757: update ANTLR to latest version
- As for the SLL lookahead, I wouldn't worry about the larger numbers, they represent the total lookahead across all in...
- 07:50 AM Feature #1757: update ANTLR to latest version
- I'm also reminded of Sam's advice from some forum: "Do not assume the lexer is fast." It might be worth profiling the...
- 07:48 AM Feature #1757: update ANTLR to latest version
- Yes, it helped a bit.
I enabled ANTLR4 profiling to see how much time is spent in each parser decision:
{{colla... - 06:42 AM Feature #1757: update ANTLR to latest version
- > ANTLR4 parsed the standard.df file in 1235103542 ns, which is about 1.23 seconds, while ANTLR2 completed the same p...
04/21/2026
- 01:28 PM Feature #1757: update ANTLR to latest version
- ANTLR3 supports @LL(k)@. But it is old and not supported and doesn't have ATN support.
There is this interesting ... - 10:23 AM Feature #1757: update ANTLR to latest version
- Paula Păstrăguș wrote:
> Also, there is an optimized fork of ANTLR4 available here: https://github.com/tunnelvisionl... - 10:22 AM Feature #1757: update ANTLR to latest version
- I'm not surprised. Consider how truly awful that result is. The content we are parsing in the @.df@ is trivial. Th...
- 08:58 AM Feature #1757: update ANTLR to latest version
- Paula Păstrăguș wrote:
> Sure, I'm currently measuring the parsing time of @standard.df@ using ANTLR4 and comparing ... - 08:28 AM Feature #1757: update ANTLR to latest version
- Also, there is an optimized fork of ANTLR4 available here: https://github.com/tunnelvisionlabs/antlr4/blob/master/doc...
- 08:16 AM Feature #1757: update ANTLR to latest version
- Sure, I'm currently measuring the parsing time of @standard.df@ using ANTLR4 and comparing it with the old ANTLR2 imp...
- 08:12 AM Feature #1757: update ANTLR to latest version
- We have a big decision to make.
It is not clear to me that ANTLR4 is the best choice. It has been optimized to ... - 07:43 AM Feature #1757: update ANTLR to latest version
- I will continue the discussion here. For context, previous relevant notes include #10804-218, #10804-220, #10804-221.
- 08:24 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- I've noticed that many builtin classes have incomplete @LegacySignature@ instances. For example @com.goldencode.p2j.o...
- 06:33 AM Feature #9638: resolve OO dependencies during parsing using annotations in already converted classes
- I've successfully integrated loading of bultin classes from jars but the current implementation is looking for class ...
- 08:21 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I've just identified the issue with my latest commit. I think, due to the build.gradle, the @*TokenTypes.java@ files ...
- 08:11 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- We have a big decision to make.
It is not clear to me that ANTLR4 is the best choice. It has been optimized to ... - 07:35 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Greg Shah wrote:
> *Unfortunately, I don't think we can disable @ALL(*)@ completely and move back to @LL(k)@ in ANTL... - 07:22 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- The supposed advantage of @ALL(*)@ is wasted on us. They designed it to trade runtime performance for a more simple ...
- 05:58 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Greg Shah wrote:
> I think we need more helper methods (outside of the parser) to reduce code like this (from @func_... - 05:52 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Here is a breakdown of how @SLL@, @LL@, @adaptivePredict@, the @ATN@, and the @lookahead DFA@ all work together in th...
- 04:40 AM Bug #11381 (Test): trunk no longer generates OpenClient proxies either via conversion or Generate...
- Branch 11381a was merged into trunk 16527 and archived.
- 04:23 AM Bug #11381 (Merge Pending): trunk no longer generates OpenClient proxies either via conversion or...
- Please merge to trunk now.
04/20/2026
- 03:28 PM Bug #11381 (Internal Test): trunk no longer generates OpenClient proxies either via conversion or...
- Dănuț Filimon wrote:
> Constantin, there are a few additional changes to review in @rules@ and @src/com/goldencode/a...
04/17/2026
- 04:15 PM Feature #7318 (Internal Test): prevent abend during conversion in case of failures when processin...
- Code Review Task Branch 7318a Revisions 16522 and 16523
I'm OK with the changes. - 04:16 AM Feature #7318 (Review): prevent abend during conversion in case of failures when processing TRPL ...
- I addressed the concern about disabling the feature where errors do not stop the conversion from running, but only re...
- 01:09 PM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I think we need more helper methods (outside of the parser) to reduce code like this (from @func_return@):...
- 01:04 PM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Hmmm. We can't use the @r=.@ approach for cases like this. The new code:...
- 11:06 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- You should now be able to see the latest version of @ProgressParser.g4@, along with the other grammars. Please note t...
- 10:53 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I committed my test project as rev *16494* (is based on 16493 + 10804a changes).
- 10:37 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I did some additional debugging, and I'm starting to think this may not actually be an ANTLR4 issue, but rather a pro...
- 09:38 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I especially would like to understand how they compare to the ANTLR2 @LL(k)@ approach.
- 09:38 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I'll take care of it once the article has been read.
- 09:36 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- > * *SLL* is fast but context insensitive and it may fail on complex grammars
> * *LL* is a bit slower, but accurate... - 09:29 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Let me create a short grammar to see if this is clearly an antlr4 bug or not. (I'm referring to tokens fetching)
- 09:26 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Based on the documentation:
* *SLL* is fast but context insensitive and it may fail on complex grammars
* *LL* is a... - 09:13 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Please provide a summary description of each of these prediction types. Also, what is the behavior of setting this v...
- 09:06 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Here's an article about @adaptive LL(*)@: https://www.antlr.org/papers/allstar-techreport.pdf I'll look into it.
- 09:02 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Neither prediction mode solved the token fetching issue after I reverted my fix. But let me surprise you even more: m...
- 08:32 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- However, I don't think adaptivePredict itself can be avoided. What we may be able to change instead is the prediction...
- 08:25 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- yes..
Here are the prediction modes: LL, LL_EXACT_AMBIG_DETECTION and SLL - 08:23 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Logically, it is an incorrect result, right? Besides being stupid it is broken. Not being able to exit the loop is ...
- 08:23 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I think by using @parser.getInterpreter().setPredictionMode(...)@, but I need to see what are the available predictio...
- 08:22 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Can we disable it?
- 08:15 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Greg Shah wrote:
> I don't understand how @adaptivePredict()@ can be so stupid. From the original @progress.g@, that... - 08:07 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- my testing project is based on trunk *16493* + 10804 changes. What if I overwrite the current version of 10804a with ...
- 08:02 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Before going further, I think you should come up with a solution for the symbol problem. That is crucial for the par...
- 08:01 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Paula Păstrăguș wrote:
> Would @ProgressParser.g4@ be sufficient? I do have a some additional changes as well, but t... - 07:59 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I don't understand how @adaptivePredict()@ can be so stupid. From the original @progress.g@, that loop can *only matc...
- 07:42 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- If you want to test the parser I think I can upload my testing project on devsrv, tmp directory.
- 07:40 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Would @ProgressParser.g4@ be sufficient? I do have a some additional changes as well, but those are currently in a tr...
- 07:37 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Please check in all your changes, even if everything is broken. I can't see any of your parser work.
- 05:28 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- PS: My goal is to get the @fwd-embedded-driver@ converted correctly. I've made progress up to line @139@ so far, wher...
- 05:26 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Current failing testcase:...
- 03:48 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I think I found the root cause! 🥳 Let me break it down for you.
The flow for a DEFINE statement currently looks li... - 03:13 AM Bug #11381 (Review): trunk no longer generates OpenClient proxies either via conversion or Genera...
- Constantin, there are a few additional changes to review in @rules@ and @src/com/goldencode/artifacts/ArtifactWorker....
- 03:12 AM Bug #11381: trunk no longer generates OpenClient proxies either via conversion or GenerateLegacyP...
- Committed *11381a/16522*. Committed the patch from #11381-6.
About the change from @src/com/goldencode/p2j/convert...
04/16/2026
- 11:42 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- You should debug into @adaptivePredict()@ in that broken case and see why it goes wrong. It is best to know why now,...
- 10:15 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I commented out the problematic adaptivePredict, and it seems to resolve the issue of fetching tokens on and on. I'll...
- 09:16 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Regarding the repeated token fetching triggered from @def_var_stmt@, and more specifically around @as_clause@, my cur...
- 09:08 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I installed an ANTLR4 plugin for IntelliJ IDEA, and it provides some useful metrics. For example, it shows the effect...
- 10:12 AM Bug #11381: trunk no longer generates OpenClient proxies either via conversion or GenerateLegacyP...
- Constantin, I posted this patch based on what you posted and the remaining problem from #11381-5. The proxies are gen...
- 09:02 AM Bug #11381: trunk no longer generates OpenClient proxies either via conversion or GenerateLegacyP...
- Constantin Asofiei wrote:
> Danut, see attached patch, it solves the case where the program is in a abl/ sub-folder ... - 08:59 AM Bug #11381: trunk no longer generates OpenClient proxies either via conversion or GenerateLegacyP...
- Danut, see attached patch, it solves the case where the program is in a abl/ sub-folder (resolved via PROPATH) - plea...
- 05:50 AM Bug #11381 (WIP): trunk no longer generates OpenClient proxies either via conversion or GenerateL...
- I updated https://proj.goldencode.com/projects/regression/wiki/Open_Regressions_in_FWD_v4#section-3
- 05:47 AM Bug #11381: trunk no longer generates OpenClient proxies either via conversion or GenerateLegacyP...
- Trunk no longer generates OpenClient proxies from .xpxg files, either via conversion or GenerateLegacyProxyOpenClient...
- 05:46 AM Bug #11381 (Test): trunk no longer generates OpenClient proxies either via conversion or Generate...
04/15/2026
- 10:06 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- The getTokens method is *not* the culprit here. I did some debugging with a very simple testcase like:...
- 05:39 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I'll investigate this next and try to confirm whether the lexer is actually tokenizing ahead to the end of file, or w...
- 05:34 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- > Here's the code:
If it is lexing all the way to the end of the file independently of the parser, that is not OK.... - 05:26 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Here's the code:...
- 05:25 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- The measurement is about token stream buffering, not actual ANTLR prediction depth.. I'll see how can I measure how m...
- 05:15 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- In ANTLR2 we introduced a very explicit @k@ value that limited the number of tokens of lookahead. In the lexer it wa...
- 05:09 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- The tests above were done with @BufferedTokenStream@. One possible direction would be to try @UnbufferedTokenStream@,...
- 03:40 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I checked to see how many buffered tokens antlr4 tend to gather, here are some results:
* tested for the failing t...
04/14/2026
- 09:56 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- > My suggestion was not to shift everything to symbols, but rather to ensure that the lexer emits the correct token f...
- 08:22 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- I’ll also do some additional research to see what can be done specifically for this test case. I haven’t committed th...
- 08:12 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Another aspect worth mentioning is related to the testing phase. If we move toward emitting tokens differently in the...
- 08:04 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Greg Shah wrote:
> Yes, it is a systemic issue with the 4GL language design itself. This is not something we can co... - 07:44 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Yes, it is a systemic issue with the 4GL language design itself. This is not something we can control.
> The more... - 07:11 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- In the ANTLR2 version, this kind of situation was handled by mutating the token type inside the parser rule. That app...
- 02:16 AM Feature #10804: create replacement AST implementation for use with ANTLR 4
- Current failing test:...
Also available in: Atom