Activity
From 10/20/2024 to 11/18/2024
11/18/2024
- 09:38 AM Bug #6389: LENGTH function with COLUMN option
- I am using tests like the one in #6389-21.
- 09:36 AM Bug #6389: LENGTH function with COLUMN option
- Did you test in both ChUI, GUI and batch process?
- 09:19 AM Bug #6389: LENGTH function with COLUMN option
- Should I commit the fix for the "Column" parameter, or fix the other ones too?
- 08:50 AM Bug #6389: LENGTH function with COLUMN option
- I have a fix for the @COLUMN@ parameter, but it looks like the same method could be used for all the parameters.
- 08:49 AM Bug #6389: LENGTH function with COLUMN option
- ...
- 07:41 AM Bug #6389: LENGTH function with COLUMN option
- I was not aware we already have it :), thank you.
- 07:32 AM Bug #6389: LENGTH function with COLUMN option
- The same class exists in FWD as @p2j/build/lib/jline-2.14.6.jar:jline.console.WCWidth@. I'm confused why you need th...
- 07:29 AM Bug #6389: LENGTH function with COLUMN option
- Constantin Asofiei wrote:
> Artur, you mean this project? https://github.com/jline/jline3
No, it it a class in the ... - 07:23 AM Bug #6389: LENGTH function with COLUMN option
- Artur, you mean this project? https://github.com/jline/jline3
Greg: please comment about BSD. - 07:21 AM Bug #6389: LENGTH function with COLUMN option
- I wrote an implementation for the @columnLength@ method, but it relies on the @jdk.internal.org.jline.utils.WCWidth@ ...
- 05:57 AM Bug #6389 (WIP): LENGTH function with COLUMN option
- 08:11 AM Bug #9350: gap marking for LOG-MANAGER attributes and methods is probably wrong
- We have analytics tooling that allows us to evaluate the level of support for each 4GL language feature. This is rep...
- 08:10 AM Bug #9350: gap marking for LOG-MANAGER attributes and methods is probably wrong
- Greg Shah wrote:
> See [[p2j:Gap Analysis]].
Where is the gap marking for @LOG-MANAGER@? - 08:06 AM Bug #9350: gap marking for LOG-MANAGER attributes and methods is probably wrong
- How is this task different from #3853?
- 08:06 AM Bug #9350: gap marking for LOG-MANAGER attributes and methods is probably wrong
- See [[p2j:Gap Analysis]].
- 08:05 AM Bug #9350: gap marking for LOG-MANAGER attributes and methods is probably wrong
- These are some items in reports for an application being evaluated.
* attributes
** @LOGGING-LEVEL@ (conversion f... - 08:02 AM Bug #9350: gap marking for LOG-MANAGER attributes and methods is probably wrong
- What is the concern? I tested what I implemented, when I implemented it.
- 07:55 AM Bug #9350 (Internal Test): gap marking for LOG-MANAGER attributes and methods is probably wrong
11/08/2024
- 08:26 AM Feature #6819: refactor FWD proxy implementation to use ReflectASM instead of Java Method reflection
- Note to self, review/explore the following things:
* How Java 17 affects lambda/method handle usage.
* Investigat...
11/01/2024
- 08:33 AM Bug #8944: FINALLY block transaction processing
- Constantin Asofiei wrote:
> So, are all cases being 'faulty' or just the @popScope@ one?
I have seen issues only ... - 08:19 AM Bug #8944: FINALLY block transaction processing
- We have FINALLY being processed in FWD, in:
* @iterateWorker@ when the block is iterating
* @processRetry@ in case ...
10/31/2024
- 03:15 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Constantin, please review.
10/30/2024
- 10:35 AM Bug #8643 (Review): ErrorManager not handling caught errors and error-status:error attribute prop...
- Rebased 8643a, to latest trunk. And fixed some history entries in revision 15528.
Committed on 8643a, revision 155... - 10:33 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Looking a bit more closely at the example from #8643-30, and the implementation of @BlockManager.processLegacyError@....
- 07:34 AM Bug #8643: ErrorManager not handling caught errors and error-status:error attribute properly
- Tested unittests with the changes from 8643a. It indeed solves a lot of tests in @service@ and some other modules. Bu...
10/29/2024
- 06:14 AM Bug #8944: FINALLY block transaction processing
- deleted
- 05:23 AM Bug #8944: FINALLY block transaction processing
- Considering that in 4GL, @finally@ is executed at the end of each iteration of the enclosing block, extracting the fi...
- 05:00 AM Bug #8944: FINALLY block transaction processing
- *Further analysis into finally blocks and transactions based on the example in #8944-1.*
A scenario without a fina...
10/28/2024
- 10:46 AM Bug #8944: FINALLY block transaction processing
- Using the @_TRANS@ VST with the examples above, I concluded that for the full transactions:
* @exclusive-lock@ forc... - 10:27 AM Bug #8944: FINALLY block transaction processing
- > _TRANS virtual system table is not supported by fwd
Correct - 10:19 AM Bug #8944: FINALLY block transaction processing
- I was trying to analyze transactions for the examples above using...
Also available in: Atom