Activity
From 03/27/2023 to 04/25/2023
04/25/2023
- 04:05 PM Feature #4065: server-side processing of client platform dependencies
- Constantin: Please review.
- 04:04 PM Feature #4065: server-side processing of client platform dependencies
- Code Review Task Branch 4065a Revisions 14521 through 14527
Overall this is a really nice update! I think the app... - 02:37 PM Bug #7301: pre-scan of a 'DEFINE BUFFER btt1 FOR btt1' from within a method
- Created task branch 7301a from trunk rev 14551.
The patch in previous note is in rev 14552. - 09:51 AM Bug #7301: pre-scan of a 'DEFINE BUFFER btt1 FOR btt1' from within a method
- The previous patch is not correct, it regresses this case:...
- 07:14 AM Bug #7301: pre-scan of a 'DEFINE BUFFER btt1 FOR btt1' from within a method
- In pre-scan, no scope is pushed for top-level blocks (as we can't track them). This case fails to parse in pre-scan:...
- 07:06 AM Bug #7301 (Closed): pre-scan of a 'DEFINE BUFFER btt1 FOR btt1' from within a method
- 12:48 PM Bug #7299: resolution of the target OO method in chained calls with poly arguments
- We convert compilable code, which this is. hIt is used heavily in a customer project so we need to get it right.
- 12:36 PM Bug #7299: resolution of the target OO method in chained calls with poly arguments
- Constantin Asofiei wrote:
> Marian, we need more tests to determine how OE behaves in this case. The problem here i... - 12:27 PM Bug #7299: resolution of the target OO method in chained calls with poly arguments
- Greg Shah wrote:
> I think this fix is needed urgently by one project. Should we merge this to trunk and 7156a now ... - 12:24 PM Bug #7299: resolution of the target OO method in chained calls with poly arguments
- I think this fix is needed urgently by one project. Should we merge this to trunk and 7156a now and then check the t...
- 12:22 PM Bug #7299: resolution of the target OO method in chained calls with poly arguments
- Code Review Task Branch 7299a Revision 14551
No objections. - 07:19 AM Bug #7299: resolution of the target OO method in chained calls with poly arguments
- Created task branch 7299a from trunk rev 14550. The patch is in rev 14551. Greg, please review.
- 05:39 AM Bug #7299: resolution of the target OO method in chained calls with poly arguments
- Constantin, will do... as a side note, imho this should not have been allowed in 4GL, it completely break any strong ...
04/24/2023
- 02:11 PM Bug #7299: resolution of the target OO method in chained calls with poly arguments
- Marian, we need more tests to determine how OE behaves in this case. The problem here is when there are multiple ove...
- 01:49 PM Bug #7299: resolution of the target OO method in chained calls with poly arguments
- In #7261, this test was found to not work properly:...
- 01:48 PM Bug #7299 (Test): resolution of the target OO method in chained calls with poly arguments
- 12:57 PM Bug #7240: conversion problem related to ENTERED in a IF expr
- Another case somehow related to #7178 - @tt1.f1 [not] entered@ must not produce a buffer reference. A fix for this ...
- 10:45 AM Bug #5276: resolve issues with multi-byte character processing
- Status on this: I'm in the middle of converting @character.java@ to use @codePointAt@ instead of @charAt@ where appro...
04/21/2023
- 10:37 AM Feature #4065: server-side processing of client platform dependencies
- Greg Shah wrote:
> The initial support was put in as branch 3821c revision 13885/13886.
Ah, I see... it should be... - 10:36 AM Feature #4065: server-side processing of client platform dependencies
- Constantin Asofiei wrote:
> When a 3821c revision is mentioned, that is a trunk revision. 3821c became trunk some ti... - 10:34 AM Feature #4065: server-side processing of client platform dependencies
- Galya Bogdanova wrote:
> Greg Shah wrote:
> > But you can look at the existing code for the model.
> If I don't kn... - 10:33 AM Feature #4065: server-side processing of client platform dependencies
- Greg Shah wrote:
> But you can look at the existing code for the model.
If I don't know the revision, how do I know... - 10:32 AM Feature #4065: server-side processing of client platform dependencies
- The initial support was put in as branch 3821c revision 13885/13886.
Additional support is written in 4065a but ha... - 10:30 AM Feature #4065: server-side processing of client platform dependencies
- Galya Bogdanova wrote:
> There is no email @merge notification for task branch 4065@ and no comment which revision i... - 10:25 AM Feature #4065: server-side processing of client platform dependencies
- There is no email @merge notification for task branch 4065@ and no comment which revision it was on trunk. How do I f...
- 09:20 AM Feature #4065: server-side processing of client platform dependencies
- Thank you for the help. I'll find the configs now on trunk.
- 09:02 AM Feature #4065: server-side processing of client platform dependencies
- Take a look at the library manager support (or memptr) in trunk.
- 08:38 AM Feature #4065: server-side processing of client platform dependencies
- When a client process accesses the server, how do you know if its a local client (on the same host) or a remote one w...
04/20/2023
- 01:55 PM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- I've created a more complete test for inferring empty dynamic DATA-SET from JSON data w/o root element (#7193-27).
N... - 06:48 AM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- Ovidiu Maxiniuc wrote:
> Review of 7193a/14544.
> * @AbstractTempTable.java@: please set the number in H entry (21)... - 05:12 AM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- The task branch 7193a was rebased to the trunk/14543.
Pushed up to revision 14551.
04/19/2023
- 04:13 PM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- Igor Skornyakov wrote:
> As far as I understand the 7193a is not reabsed to lasterst trunk.
> > No, I've extracte... - 04:05 PM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- Vladimir Tsichevski wrote:
> Igor Skornyakov wrote:
>
> > The @{ "Customer": [ { "customerName": "John Smith", "... - 03:53 PM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- Igor Skornyakov wrote:
> The @{ "Customer": [ { "customerName": "John Smith", "customerNum": 10}, { "customerNam... - 03:48 PM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- Ovidiu Maxiniuc wrote:
> Review of 7193a/14544.
>
> Good job! A lot of code with adjustments for existing feature... - 03:36 PM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- Review of 7193a/14544.
Good job! A lot of code with adjustments for existing features. Here are some notes, most o... - 02:45 PM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- Vladimir Tsichevski wrote:
> I am running OEUnit fixture test class:
>
> [...]
>
> In this class a fixture is ... - 02:20 PM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- I am running OEUnit fixture test class:...
04/18/2023
- 05:52 PM Feature #6422 (WIP): implement auditing support including AUDIT-POLICY and AUDIT-CONTROL
- 11:02 AM Bug #7247: Dataset:READ-XML does nothing
- Created task branch 7247a.
- 09:58 AM Feature #6428: implement IS-LEAD-BYTE() built-in function
- Vladimir Tsichevski wrote:
> Greg Shah wrote:
> > > I think, the unit testing for the function can be done in the f... - 08:29 AM Feature #6428: implement IS-LEAD-BYTE() built-in function
- Greg Shah wrote:
> > I think, the unit testing for the function can be done in the form of JUnit5 Jupiter engine tes... - 08:25 AM Feature #6428: implement IS-LEAD-BYTE() built-in function
- > I think, the unit testing for the function can be done in the form of JUnit5 Jupiter engine tests at the Java level...
- 07:36 AM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- Well, all tests passed.
Committed to 7193a/14544.
Please review.
Thank you. - 06:42 AM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- Igor Skornyakov wrote:
> Igor Skornyakov wrote:
> > However these additional testes reveal a strange problem with W... - 04:47 AM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- Igor Skornyakov wrote:
> However these additional testes reveal a strange problem with WRITE-XML for the PARENT-ID-R...
04/17/2023
- 04:11 PM Feature #6428: implement IS-LEAD-BYTE() built-in function
- I think, the unit testing for the function can be done in the form of JUnit5 Jupiter engine tests at the Java level, ...
- 11:22 AM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- Fixed issues with READ-JSON for empty dynamic DATA-SET revealed by additional tests.
Committed to 7193a/14543.
Ho... - 03:32 AM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- Just noticed.
When running the attached test I see multiple message like this...
04/16/2023
- 02:35 AM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- Igor Skornyakov wrote:
> Added support for inferring empty dynamic DATA-SET from JSON data. Fixed support for PARENT...
04/15/2023
- 02:32 PM Bug #7247 (WIP): Dataset:READ-XML does nothing
- 02:31 PM Bug #7193 (Review): READ-JSON is not supported for the "LONGCHAR" source type
- Added support for inferring empty dynamic DATA-SET from JSON data. Fixed support for PARENT-ID-RELATION in WRITE-JSON...
- 12:19 PM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- I've encountered the following problem.
On inferring @DATA-SET@ from JSON data with @READ-JSON@ the @NESTED@ @DATA-R...
04/14/2023
- 01:02 PM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- Inferring empty dynamic DATA-SET from JSON data is mostly finished.
Committed to 7193a/14539.
The tables looks th... - 09:02 AM Feature #6422: implement auditing support including AUDIT-POLICY and AUDIT-CONTROL
- Please do the following:
* Review #6422 and the 4GL facilities it is intended to implement.
* Write testcases and... - 09:02 AM Feature #6420: implement the AUDIT-ENABLED() built-in function
- This is meant to report on whether the 4GL-compatible auditing support is activated. That means it is dependent upon...
04/13/2023
- 05:17 PM Feature #6420 (WIP): implement the AUDIT-ENABLED() built-in function
- 04:52 PM Feature #6420: implement the AUDIT-ENABLED() built-in function
- How should we implement this feature? Should we just add a flag into @directory/client.xml@ or should we replicate th...
04/12/2023
- 02:14 PM Bug #7272: RUN ... NO-ERROR must log the 'missing.p was not found' message, always.
- This bug already exists in trunk, it came up in a discussion when debugging a customer's application.
- 02:12 PM Bug #7272: RUN ... NO-ERROR must log the 'missing.p was not found' message, always.
- I mentioned 'log' in the title and previous entry, but this is also about displaying the error message to the user. ...
- 02:00 PM Bug #7272: RUN ... NO-ERROR must log the 'missing.p was not found' message, always.
- This program:...
- 01:53 PM Bug #7272 (Closed): RUN ... NO-ERROR must log the 'missing.p was not found' message, always.
04/10/2023
- 10:53 AM Feature #7126: replace 'new unknown()' with 'unknown.INSTANCE' in FWD conversion and runtime
- This task isn't a priority right now.
- 10:49 AM Feature #7126: replace 'new unknown()' with 'unknown.INSTANCE' in FWD conversion and runtime
- Constantin Asofiei wrote:
> > # calling the @unknown.instantiateUnknown()@, this function just returns the @unknow... - 10:45 AM Feature #7126: replace 'new unknown()' with 'unknown.INSTANCE' in FWD conversion and runtime
- Vladimir Tsichevski wrote:
> I can take this task.
Greg?
> # calling @new unknown()@, we want to get rid of thi... - 10:02 AM Feature #7126: replace 'new unknown()' with 'unknown.INSTANCE' in FWD conversion and runtime
- I can take this task.
A question: currently there is 3 ways to obtain the @unknown@ value:
# calling @new unkno... - 08:24 AM Bug #7250 (Closed): PROMPT-FOR with a table field reference resolves to NO-REFERENCE in OpenEdge
- 07:55 AM Bug #7250: PROMPT-FOR with a table field reference resolves to NO-REFERENCE in OpenEdge
- 7199b/14533 was merged to trunk rev 14528 and archived.
- 08:23 AM Bug #7243 (Closed): collision between YEAR function and a perm table abbreviated name
- 07:55 AM Bug #7243: collision between YEAR function and a perm table abbreviated name
- 7199b/14533 was merged to trunk rev 14528 and archived.
- 08:23 AM Bug #7240 (Closed): conversion problem related to ENTERED in a IF expr
- 07:55 AM Bug #7240: conversion problem related to ENTERED in a IF expr
- 7199b/14533 was merged to trunk rev 14528 and archived.
04/06/2023
- 10:46 AM Feature #4065: server-side processing of client platform dependencies
- Greg/Hynek: for server-side memptrs, we still have the problem when the memory address is incoming from a OS library ...
04/05/2023
- 04:04 PM Bug #7250 (Test): PROMPT-FOR with a table field reference resolves to NO-REFERENCE in OpenEdge
- Code Review Task Branch 7199b Revision 14529
No objection. - 04:02 PM Bug #7243 (Test): collision between YEAR function and a perm table abbreviated name
- Code Review Task Branch 7199b Revision 14526
No objection. - 03:55 PM Bug #7240 (Test): conversion problem related to ENTERED in a IF expr
- 03:55 PM Bug #7240: conversion problem related to ENTERED in a IF expr
- Code Review Task Branch 7199b Revisions 14524, 14527 and 14528
No objections. - 03:42 PM Feature #4065: server-side processing of client platform dependencies
- In regard to the shell commands, I think it is OK if we require that the commands meet one of these criteria:
* It... - 02:51 PM Feature #6428: implement IS-LEAD-BYTE() built-in function
- In 4GL, the CPINTERNAL attribute is rather a constant than a variable. It is configured when the application is execu...
- 12:37 PM Feature #6428: implement IS-LEAD-BYTE() built-in function
- I think we have this same problem for all of our I18N tests, many of which still need to be written.
> Because it... - 10:57 AM Feature #6428: implement IS-LEAD-BYTE() built-in function
- I've hit a wall here, as I misunderstood some Progress behaviour. During my initial exploration on the OpenEdge syste...
- 12:51 PM Feature #6431: implement support to allow CPINTERNAL set to UTF-8 and CP936
- We have a customer that needs to be able to set UTF-8 or CP963 as the @CPINTERNAL@. We may have some problems with d...
- 12:43 PM Bug #4766: fix CHR and ASC
- What is left to do in this task? Please note that in #6428 Joe is fixing an issue related to lead-byte processing in...
- 10:17 AM Feature #6425: SESSION handle features
- I created some tests under @testcases/session/session_features.p@. Please review.
- 07:01 AM Feature #6410: implement additional built-in OO classes/interfaces
- Greg Shah wrote:
> Marian: Please summarize the current level of conversion support for all of the classes #6410-1. ...
04/04/2023
- 03:43 PM Feature #4065 (Review): server-side processing of client platform dependencies
- 03:42 PM Feature #4065: server-side processing of client platform dependencies
- The server-side shell execution will require more thought. For the file system it is straightforward to get a canonic...
- 03:38 PM Feature #4065: server-side processing of client platform dependencies
- 4065a revision 14527 implements server side file-system and file-based stream (based on @FileStream@ and @DirStream@)...
- 12:37 PM Feature #6428: implement IS-LEAD-BYTE() built-in function
- Greg Shah wrote:
> No, you haven't missed anything. See #3827. The related code in 3827a is close to merging to tr... - 11:50 AM Feature #6411 (Closed): LOB-DIR I/O option support
- 3821c replaced trunk in trunk revision 14472 (we copied over trunk with 3821c rev 14472).
- 11:28 AM Feature #6411: LOB-DIR I/O option support
- Greg Shah wrote:
> In what revision of trunk can these changes be found?
>
It was in last commit of the @3821c@... - 10:55 AM Feature #6411: LOB-DIR I/O option support
- In what revision of trunk can these changes be found?
Are there any open items? - 10:36 AM Feature #6411 (Review): LOB-DIR I/O option support
- 10:36 AM Feature #6411 (WIP): LOB-DIR I/O option support
- 10:24 AM Feature #6411: LOB-DIR I/O option support
- Greg Shah wrote:
> Didn't we implement this recently?
Yes, we did. - 10:19 AM Feature #6411: LOB-DIR I/O option support
- Didn't we implement this recently?
- 10:33 AM Feature #6410: implement additional built-in OO classes/interfaces
- Marian: Please summarize the current level of conversion support for all of the classes #6410-1. We need all of thes...
- 10:08 AM Feature #6300 (Closed): class definitions with USE-WIDGET-POOL
- 09:56 AM Bug #7250 (Review): PROMPT-FOR with a table field reference resolves to NO-REFERENCE in OpenEdge
- I've fixed this in 7199b/14529
- 09:33 AM Bug #7250: PROMPT-FOR with a table field reference resolves to NO-REFERENCE in OpenEdge
- Greg Shah wrote:
> The warning is because the code as written is useless.
It's not entirely useless - the customer'... - 09:15 AM Bug #7250: PROMPT-FOR with a table field reference resolves to NO-REFERENCE in OpenEdge
- The warning is because the code as written is useless. The user will go into edit mode, make changes and then the cha...
- 09:04 AM Bug #7250: PROMPT-FOR with a table field reference resolves to NO-REFERENCE in OpenEdge
- There is a weird behavior in OpenEdge. This test:...
- 09:02 AM Bug #7250 (Closed): PROMPT-FOR with a table field reference resolves to NO-REFERENCE in OpenEdge
- 06:56 AM Feature #6425: SESSION handle features
- Theodoros Theodorou wrote:
> The task is ready for review. Should I also create a test in testcases?
Yes, please do. - 03:18 AM Bug #7240: conversion problem related to ENTERED in a IF expr
- Another issue is related to @frame f1 ... not entered@ version - the fix is in 7199b/14528.
04/03/2023
- 05:09 PM Feature #6425: SESSION handle features
- The task is ready for review. Should I also create a test in testcases?
- 05:06 PM Feature #6425 (Review): SESSION handle features
- 04:53 PM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- Vladimir Tsichevski wrote:
> Igor, would you take a look at #7247, please. I think, both issues are closely related.... - 04:43 PM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- Igor, would you take a look at #7247, please. I think, both issues are closely related.
- 04:50 PM Bug #7247: Dataset:READ-XML does nothing
- Vladimir Tsichevski wrote:
> The test case is:
> [...]
>
> The test compiles and runs OK. But in FWD the @READ-X... - 04:40 PM Bug #7247: Dataset:READ-XML does nothing
- The test case is:...
- 04:36 PM Bug #7247 (Closed): Dataset:READ-XML does nothing
- 04:22 PM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Constantin Asofiei wrote:
> I think the solution would be in literals.rules on line 371:
> to add a @!(isNote("wrap... - 10:34 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Constantin Asofiei wrote:
> It means they are added by the parser. I assume you see other @byrule-@ annotations i... - 09:34 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Vladimir Tsichevski wrote:
> Constantin Asofiei wrote:
>
> > OTOH, we should find who sets the @wrap@ annotation ... - 09:31 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Constantin Asofiei wrote:
> OTOH, we should find who sets the @wrap@ annotation for the literal - did you convert ... - 09:12 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- The repo 7184a was created for the fix, and the regression test task #7245.
- 02:45 PM Feature #6428: implement IS-LEAD-BYTE() built-in function
- No, you haven't missed anything. See #3827. The related code in 3827a is close to merging to trunk. Vladimir is wr...
- 02:39 PM Feature #6428: implement IS-LEAD-BYTE() built-in function
- I had misread the current docs, and didn't use ABLUnit for tests (instead writing standalone tests). I'm in the proce...
- 06:11 AM Feature #3853: implement LOG-MANAGER runtime
- @LOG-ENTRY-TYPES@ and @LOGGING-LEVEL@ are @LOG-MANAGER@ attributes that can be changed in the internal procedure runn...
- 05:34 AM Feature #3853: implement LOG-MANAGER runtime
- Appservers have the following logging configs in OE Explorer:
* srvrLogFile - by default @{WorkPath}\%appservername%... - 03:47 AM Feature #3853: implement LOG-MANAGER runtime
- Answering to #5753#note-113 :
Constantin Asofiei wrote:
> From this, we know:
> * changing @LOGFILE-NAME@ does n... - 01:41 AM Bug #7240: conversion problem related to ENTERED in a IF expr
- The fix is in 7199b/14527
04/02/2023
- 03:41 PM Bug #7240: conversion problem related to ENTERED in a IF expr
- There is another issue related to INPUT/ENTERED - fields need to be treated the same way as vars in @input_functions....
03/31/2023
- 06:21 PM Feature #6428: implement IS-LEAD-BYTE() built-in function
- > but without knowing why that check was there in the first place I'd be hesitant to remove it.
If I recall correc... - 05:24 PM Feature #6428: implement IS-LEAD-BYTE() built-in function
- Summary of findings for today:
* I've confirmed that @character.chr@ behaves differently to Progress' @CHR@ for mu... - 12:26 PM Feature #6428: implement IS-LEAD-BYTE() built-in function
- Good work, yes this makes sense.
- 03:02 PM Bug #7243 (Review): collision between YEAR function and a perm table abbreviated name
- The fix is in 7199b/14526.
- 01:57 PM Bug #7243 (WIP): collision between YEAR function and a perm table abbreviated name
- 01:55 PM Bug #7243: collision between YEAR function and a perm table abbreviated name
- The patch for this seems to be:...
- 01:36 PM Bug #7243: collision between YEAR function and a perm table abbreviated name
- This test fails to convert:...
- 01:35 PM Bug #7243 (Closed): collision between YEAR function and a perm table abbreviated name
- 11:51 AM Bug #7240 (Review): conversion problem related to ENTERED in a IF expr
- The fix is in 7199b/14524
- 03:19 AM Bug #7240: conversion problem related to ENTERED in a IF expr
- The recreate is this:...
- 03:19 AM Bug #7240 (Closed): conversion problem related to ENTERED in a IF expr
- 07:53 AM Feature #4065: server-side processing of client platform dependencies
- From email:
>>> Hynek wrote:
>>>
>>> I meant the loading resources for the UI (icons, bitmaps). I got your point... - 07:22 AM Feature #4065: server-side processing of client platform dependencies
- > what do you think?
I think this is a discussion that is unrelated to this task. Yes, we probably have a bug in ... - 07:15 AM Feature #4065: server-side processing of client platform dependencies
- > but server-side processing is required only by legacy streams (used by INPUT/OUTPUT statements) and other cases whe...
- 03:08 AM Feature #4065: server-side processing of client platform dependencies
- Roger Borrello wrote:
> I have a question about this task... In #4938-52 I need to configure the web client such tha...
03/30/2023
- 03:09 PM Feature #4065: server-side processing of client platform dependencies
- I have a question about this task... In #4938-52 I need to configure the web client such that we have this in the dir...
- 01:15 PM Feature #4065: server-side processing of client platform dependencies
- Constantin Asofiei wrote:
> Hynek Cihlar wrote:
> > Constantin, see #4065-59 and the related where we discussed thi... - 11:16 AM Feature #4065: server-side processing of client platform dependencies
- Hynek Cihlar wrote:
> Constantin, see #4065-59 and the related where we discussed this.
OK, but when server-side st... - 03:12 AM Feature #4065: server-side processing of client platform dependencies
- Constantin Asofiei wrote:
> Greg, correct me if I'm wrong, but server-side processing is required only by legacy str... - 03:08 AM Feature #4065: server-side processing of client platform dependencies
- Greg, correct me if I'm wrong, but server-side processing is required only by legacy streams (used by INPUT/OUTPUT st...
- 03:02 AM Feature #4065: server-side processing of client platform dependencies
- Constantin Asofiei wrote:
> From Hynek via email:
> > Changing the direct IO in the client process to go through a ... - 02:59 AM Feature #4065: server-side processing of client platform dependencies
- From Hynek via email:
> Changing the direct IO in the client process to go through a remoted object on the server wi... - 02:25 AM Feature #4065: server-side processing of client platform dependencies
- I rebased 4065a against trunk revision 14520.
- 12:33 PM Feature #6428: implement IS-LEAD-BYTE() built-in function
- Here's a short summary of findings from today, I'll follow up with a status update shortly.
Greg Shah wrote:
> ... - 02:40 AM Feature #6428: implement IS-LEAD-BYTE() built-in function
- Roughly, this seems right.
# Before you go very far, please implement the 4GL testcase(s) to ensure we understand ... - 11:39 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Vladimir Tsichevski wrote:
> # convert (wrap) values to the expected type is cases the usage requires it (to use val... - 11:34 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Constantin Asofiei wrote:
> I think the solution would be in literals.rules on line 371:
> [...]
> to add a @!(isN... - 11:20 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- I think the solution would be in literals.rules on line 371:...
- 07:16 AM Feature #6497: add equivalent support for the -T command line option
- The branch 6497a has been rebased to trunk 14521. The new rev no is 14526.
Please review it and let me know if I c... - 04:25 AM Feature #3853: implement LOG-MANAGER runtime
- The tests Constantin did for #5701#note-86 made me think about the appserver agent logs.
The implementation in #57...
03/29/2023
- 04:59 PM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- First time the literal is wrapped as a parameter in @expression.rules@:...
- 03:17 PM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- If I remove the "wrap_parameter" annotation from the literal, both OO method and function calls convert correctly wit...
- 02:28 PM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Vladimir Tsichevski wrote:
> > * we will need to regression test the conversion of the original app where this was ... - 02:19 PM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Constantin Asofiei wrote:
> OK, lets back-track a little. Sorry I was so abrupt in the initial note, I was expectin... - 12:41 PM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- OK, lets back-track a little. Sorry I was so abrupt in the initial note, I was expecting a pin-point fix, not a full...
- 12:01 PM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Constantin Asofiei wrote:
> Vladimir Tsichevski wrote:
> > Constantin Asofiei wrote:
> > > There can be nested PLU... - 11:53 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Vladimir Tsichevski wrote:
> Constantin Asofiei wrote:
> > There can be nested PLUS ASTs, with complex expression w... - 11:51 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Constantin Asofiei wrote:
> There can be nested PLUS ASTs, with complex expression with or without STRING literal.
... - 11:34 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Why did you remove the @descent-rules@ portion? There can be nested PLUS ASTs, with complex expression with or witho...
- 11:30 AM Bug #7184 (Review): Incorrect conversion of concatenated string literals to a LONGCHAR
- Constantin Asofiei wrote:
> Vladimir Tsichevski wrote:
> > Constantin Asofiei wrote:
> >
> > > * copy all annota... - 11:00 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Vladimir Tsichevski wrote:
> Constantin Asofiei wrote:
>
> > * copy all annotations from @ref2@ to the @ref@ AST
... - 10:58 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Constantin Asofiei wrote:
> * copy all annotations from @ref2@ to the @ref@ AST
Is there a nice way to do this ... - 10:56 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Vladimir Tsichevski wrote:
> Seems, we need to transfer the annotations from the @PLUS@ node, not from the first arg... - 10:55 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Constantin Asofiei wrote:
> Vladimir Tsichevski wrote:
> > The question is which of 3 ways of *fixing* this problem... - 10:41 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Vladimir Tsichevski wrote:
> The question is which of 3 ways of *fixing* this problem to choose? :-(
First, you nee... - 10:33 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Constantin Asofiei wrote:
> Somewhere in TRPL (I think annotations) we transform this AST:
> [...]
> to this AST:
... - 10:27 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Somewhere in TRPL (I think annotations) we transform this AST:...
- 10:23 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Constantin Asofiei wrote:
> Please attach also the AST from the F2 phase (after parsing) and also the .cache for t... - 10:18 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Vladimir Tsichevski wrote:
> Constantin Asofiei wrote:
> > What's the full AST for the method call @testMethod("asd... - 10:17 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- Constantin Asofiei wrote:
> What's the full AST for the method call @testMethod("asdf" + "qwerty").@?
I've attach... - 10:12 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- What's the full AST for the method call @testMethod("asdf" + "qwerty").@?
- 10:11 AM Bug #7184: Incorrect conversion of concatenated string literals to a LONGCHAR
- I need some help from TRPL gurus in deciding how to solve this issue. I see the following variants:
# explicitly c... - 03:14 PM Feature #6428: implement IS-LEAD-BYTE() built-in function
- It's taken me a bit of time to grok the @Text@ class, and how ABL codepages correspond to JVM ones, but I believe I h...
- 06:19 AM Feature #6497: add equivalent support for the -T command line option
- The branch 6497a has been rebased to trunk 14519. The new rev no is 14524.
- 02:29 AM Feature #6497: add equivalent support for the -T command line option
- Theodoros Theodorou wrote:
> Please review (6497a/14502)
Looks good, thanks.
03/28/2023
- 07:38 PM Bug #7184 (WIP): Incorrect conversion of concatenated string literals to a LONGCHAR
- In the course of string literal concatenation the original annotation info is lost.
Here is how a string literal e... - 10:21 AM Feature #6497: add equivalent support for the -T command line option
- Please review (6497a/14502)
- 03:49 AM Feature #6497: add equivalent support for the -T command line option
- Review for 6497a/14501:
* ClientCore, ClientParameters, StandardServer - please add history entries
* @Utils.getTmp... - 02:54 AM Feature #6428: implement IS-LEAD-BYTE() built-in function
- This task is to implement the runtime support for @IS-LEAD-BYTE()@. Conversion support is already complete (search o...
03/27/2023
- 04:08 PM Feature #6497: add equivalent support for the -T command line option
- Please review again (6497a/14501)
- 11:59 AM Bug #7193: READ-JSON is not supported for the "LONGCHAR" source type
- Fixed READ-JSON for static DATA-SET with NESTED/FOREIGN-KEY-HIDDEN relations.
Committed to 7193a/14508.
Working i... - 04:19 AM Bug #7202 (Closed): 'accum' frame-level widget can have widget options
- 04:18 AM Bug #7203 (Closed): INIT clause for datetime var copied from 'like' phrase
- 04:18 AM Bug #7204 (Closed): method overload with dataset/temp-table parameters uses the index at the para...
- 04:18 AM Bug #7206 (Closed): shared frame defined with the same name but different widgets
- 04:18 AM Bug #7215 (Closed): 'display v @ ch' - v gets added to the ch's frame
- 03:37 AM Feature #4382 (Closed): implement configurable directory override for PROGRESS global variable
- 03:36 AM Feature #6421 (Closed): finish GENERATE-RANDOM-KEY support
Also available in: Atom