Project

General

Profile

Activity

From 05/20/2026 to 06/18/2026

06/17/2026

09:38 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
Greg Shah wrote:
> > [...]
>
> The core issue here is that you are using @closestPeerId@ which is going to be in ... Dănuț Filimon
08:56 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
> ... Greg Shah
08:28 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
Alright, so I got to into a point where the literal generates in the block instead of the variable definition.
The... Dănuț Filimon
06:36 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
Dănuț Filimon wrote:
> Greg Shah wrote:
> > > The main issue I have now is @var char c1 = "1".@ ,this is mostly rel... Greg Shah
06:30 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
Greg Shah wrote:
> > The main issue I have now is @var char c1 = "1".@ ,this is mostly related to @convert/literals.... Dănuț Filimon

06/16/2026

10:26 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
> The main issue I have now is @var char c1 = "1".@ ,this is mostly related to @convert/literals.rules@ and when shou... Greg Shah
10:03 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
Greg Shah wrote:
> I'd prefer not to do that.
>
> Please show the output that is being generated incorrectly alon... Dănuț Filimon
08:18 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
I'd prefer not to do that.
Please show the output that is being generated incorrectly along with the 4GL and the AST. Greg Shah

06/15/2026

10:03 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
Greg, is the option of adding a new token like @VAR_DEF_ITEM@ that will replace @SYMBOL@ in @VAR_DEF_LIST@? I have th... Dănuț Filimon

06/12/2026

09:28 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
Slight issues with the current way we annotate variables, for a DEFINE VARIABLE we'll just annotate the DEFINE_VARIAB... Dănuț Filimon

06/11/2026

08:33 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
@var char[3] c1 = ["1", "2", "3"].@ also works after a few small adjustments.
Right now, I am approaching @var cha... Dănuț Filimon
07:34 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
I was getting too complicated and missed a lot of details, I should've just piggy bagged the DEFINE_VARIABLE implemen... Dănuț Filimon

06/10/2026

09:28 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
Ignore my last comment, I forgot a patch. Dănuț Filimon
09:25 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
Greg Shah wrote:
> You should be trying for something like this:
>
> [...]
>
> I've removed the annotations fo... Dănuț Filimon
09:21 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
You should be trying for something like this:... Greg Shah
08:44 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
The current problem I am working on is the definition of @var char[3] c1 = [1,2,3]@, this generates the following ast... Dănuț Filimon
02:52 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
Greg Shah wrote:
> Also, I should note that the @EQUALS@ node will need to have its type rewritten as @ASSIGN@. Loo... Dănuț Filimon

06/09/2026

10:25 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
Also, I should note that the @EQUALS@ node will need to have its type rewritten as @ASSIGN@. Look at existing gramma... Greg Shah

06/08/2026

11:08 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
Yes, the use of @^@ in @eq:EQUALS^@ overrides the @makeASTRoot()@ and forces the @EQUALS@ to be the root node.
I s... Greg Shah
09:25 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
I've worked on the changes from the review and the only problem I am facing right now is resolving the qualified name... Dănuț Filimon

06/05/2026

04:53 PM Feature #9767: Support the new VAR statement introduced in Progress 12.x
Code Review Task Branch 9767a Revision 16564
Overall, this is quite close. Here are changes I'd like to see:
1... Greg Shah

06/04/2026

07:51 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
Committed *9767a/16564*. Added partial VAR statement support and ParserTestDriver.java to be used with harness.
I ... Dănuț Filimon

06/03/2026

07:27 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
That is OK, remember that we don't have syntax checking support in FWD until #3882. So long as the tests exist and "... Greg Shah
04:48 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
I ran the harness against the failing tests and found errors such as:... Dănuț Filimon

05/29/2026

05:41 AM Bug #4602: fixes for OO 4GL and structured error handling
Rebase 4602a to trunk rev. 16588. Eduard Soltan

05/28/2026

07:46 AM Feature #9767: Support the new VAR statement introduced in Progress 12.x
I looked a lot more into the lexer and preprocessor tests, but I can't figure out how to generate the OE baselines.
... Dănuț Filimon

05/27/2026

09:25 AM Feature #6407 (Review): name_map.xml improvements
Committed *6407b/16578*. Added inHandleProc to override the handle and make sure TARGET-PROCEDURE is set properly.
... Dănuț Filimon

05/26/2026

07:04 AM Feature #6407: name_map.xml improvements
I have some problems figuring out what is wrong with the changes from the last commit, the only difference I can find... Dănuț Filimon

05/25/2026

04:49 AM Feature #6407: name_map.xml improvements
Constantin Asofiei wrote:
> Danut, please create a standalone test for the 16577 commit.
>
> The resolvers must n... Dănuț Filimon

05/22/2026

10:08 AM Feature #6407: name_map.xml improvements
Danut, please create a standalone test for the 16577 commit.
The resolvers must not have dependencies on each othe... Constantin Asofiei
10:04 AM Feature #6407 (WIP): name_map.xml improvements
3 tests remain to be investigated and fixed. Dănuț Filimon
09:07 AM Feature #6407: name_map.xml improvements
Committed *6407b/16577*. Added 2767 error handling and fixed the remaining scenario where the function declaration is... Dănuț Filimon

05/21/2026

07:28 AM Feature #6407: name_map.xml improvements
Dănuț Filimon wrote:
> * @hpUtils = this-procedure.@ to @hpUtils = ?.@
This needs to be fixed in FWD.
> * removed ... Constantin Asofiei
07:26 AM Feature #6407: name_map.xml improvements
Constantin Asofiei wrote:
> Looks good. Please also test what happens if @hpUtils@ in test2.p or in start.p is unkn... Dănuț Filimon
07:04 AM Feature #6407: name_map.xml improvements
Looks good. Please also test what happens if @hpUtils@ in test2.p or in start.p is unknown. Constantin Asofiei
06:40 AM Feature #6407 (Review): name_map.xml improvements
I committed *6407b/16576* to fix how the IN-HANDLE/local implementation are resolved.
Constantin, please take a lo... Dănuț Filimon
04:14 AM Feature #6407: name_map.xml improvements
Constantin Asofiei wrote:
> * @InternalEntryKey@ needs to have also as part of the key the @IN handle@ flag (only th... Constantin Asofiei
04:11 AM Feature #6407: name_map.xml improvements
Danut, this is part of a bug which exists already in trunk:
* test1.p... Constantin Asofiei
03:30 AM Feature #6407: name_map.xml improvements
Constantin Asofiei wrote:
> Please post a standalone test.
This is the test case.... Dănuț Filimon

05/20/2026

09:21 AM Feature #6407: name_map.xml improvements
Please post a standalone test. Constantin Asofiei
08:12 AM Feature #6407 (WIP): name_map.xml improvements
Constantin, I found a scenario where we need the @jname@ in the LegacySignature. The following stack trace creates an... Dănuț Filimon
 

Also available in: Atom