Activity
From 06/15/2020 to 07/14/2020
07/14/2020
- 02:19 PM Bug #4754: DYNAMIC-FUNCTION parsing fails when first parameter is not an expression
- > It's not the same as a function call parameter.
In what way?
We know that the parameter must be an @expr@. T... - 11:57 AM Bug #4754: DYNAMIC-FUNCTION parsing fails when first parameter is not an expression
- Greg Shah wrote:
> The first parameter can be an arbitrarily complex sub-expression like @something + func(handle:bl...
07/13/2020
- 10:21 AM Bug #4754: DYNAMIC-FUNCTION parsing fails when first parameter is not an expression
- The first parameter can be an arbitrarily complex sub-expression like @something + func(handle:blah:blah:method(), ob...
- 10:12 AM Bug #4754: DYNAMIC-FUNCTION parsing fails when first parameter is not an expression
- Why is the 1st parameter of @KW_DYN_FUNC@ handled the same as the other parameters, when it is the _function-name_, n...
- 09:12 AM Bug #4754: DYNAMIC-FUNCTION parsing fails when first parameter is not an expression
- If you are sure that this is procedure handle syntax instead of widget qualifier syntax, then we may need a different...
- 08:46 AM Bug #4754: DYNAMIC-FUNCTION parsing fails when first parameter is not an expression
- @hFunc:NAME@ is a character, which in the DYNAMIC-FUNCTION's syntax for the first argument (@function-name[ IN proc-h...
- 08:33 AM Bug #4754: DYNAMIC-FUNCTION parsing fails when first parameter is not an expression
- The 4GL in the ADM2 @panel.p@ is:...
- 03:16 AM Bug #4754: DYNAMIC-FUNCTION parsing fails when first parameter is not an expression
- What's the generated Java code for this call? The @dynamic_function_func@ rule checks for @func_call_parm[false] (in_...
- 12:07 AM Bug #4754: DYNAMIC-FUNCTION parsing fails when first parameter is not an expression
- Greg Shah wrote:
> Because the 2nd case is not supposed to match an @in_procedure_clause@. The 2nd usage is an attr...
07/12/2020
- 06:10 PM Bug #4754: DYNAMIC-FUNCTION parsing fails when first parameter is not an expression
- Because the 2nd case is not supposed to match an @in_procedure_clause@. The 2nd usage is an attribute that is being ...
- 06:07 PM Bug #4754: DYNAMIC-FUNCTION parsing fails when first parameter is not an expression
- From Roger:
Why would @widget_qualifier@ be parsing, instead of @dynamic_function_func@... - 06:06 PM Bug #4754: DYNAMIC-FUNCTION parsing fails when first parameter is not an expression
- Roger Borrello wrote:
> It is like the @IN@ is never parsed.
No, the @IN@ is seen but the following token is unre... - 05:37 PM Bug #4754: DYNAMIC-FUNCTION parsing fails when first parameter is not an expression
- Added testcase @uast/handle/handle_attr_dyn_func.p@
- 05:31 PM Bug #4754: DYNAMIC-FUNCTION parsing fails when first parameter is not an expression
- The second @DYNAMIC-FUNCTION@ call fails to parse:...
- 05:24 PM Bug #4754 (Closed): DYNAMIC-FUNCTION parsing fails when first parameter is not an expression
07/08/2020
07/07/2020
- 09:26 AM Bug #4741: RUN statement with a path to a procedure that does not have any extension fails to be ...
- > It can be a @.x@, @.k@, @.tt@
And 4GL doesn't care about the extension, @RUN@ will work - only @.r@ is assumed if... - 09:25 AM Bug #4741: RUN statement with a path to a procedure that does not have any extension fails to be ...
- Roger Borrello wrote:
> ... but if there is a ".w" and ".p", we may have to enforce a precedence determined by testc... - 09:02 AM Bug #4741: RUN statement with a path to a procedure that does not have any extension fails to be ...
- Constantin Asofiei wrote:
> Greg, you are correct. We need more testcases to find every case.
>
> For now, can i... - 06:18 AM Bug #4741: RUN statement with a path to a procedure that does not have any extension fails to be ...
- Greg, you are correct. We need more testcases to find every case.
For now, can it be enough to check if the last ... - 05:57 AM Bug #4741: RUN statement with a path to a procedure that does not have any extension fails to be ...
- Relative paths @./@ and @../../something/else/../blah/@ are possible. It is also legal to include @.@ in random part...
- 08:27 PM Bug #4741: RUN statement with a path to a procedure that does not have any extension fails to be ...
- Checked in updates to @3821c-11389@ that don't have the @pname.indexOf('.') < 0)@ check. I am open to changing, just ...
07/06/2020
- 10:52 AM Bug #4734: Invalid string to date conversion for non-"mm/dd/yyyy" format
- > Which FWD branch/revision?
I've tested it against trunk rev 11347. - 10:04 AM Bug #4741: RUN statement with a path to a procedure that does not have any extension fails to be ...
- Is it possible to have @.@ in your path (or filename) that might fail that test?
- 09:51 AM Bug #4741: RUN statement with a path to a procedure that does not have any extension fails to be ...
- Change the test to this: @if (extProg == null && pname.indexOf('.') < 0)@.
- 09:49 AM Bug #4741: RUN statement with a path to a procedure that does not have any extension fails to be ...
- Constantin Asofiei wrote:
> Instead, you need to do this:
> # if the exact match of @pname@ is found, use that.
> ... - 09:16 AM Bug #4741: RUN statement with a path to a procedure that does not have any extension fails to be ...
- Roger Borrello wrote:
> In the debugger I noticed that the procedure name came into the @convertName@ method first, ... - 09:06 AM Bug #4741: RUN statement with a path to a procedure that does not have any extension fails to be ...
- In the debugger I noticed that the procedure name came into the @convertName@ method first, without a path in front o...
07/04/2020
- 01:00 PM Bug #4741: RUN statement with a path to a procedure that does not have any extension fails to be ...
- I forgot to use this task for this...
I asked about the existing code making an assumption that it is rcode. Howev...
07/03/2020
- 05:54 PM Bug #4741: RUN statement with a path to a procedure that does not have any extension fails to be ...
- He was talking about @SourceNameMapper.convertName@ at line 1395.
The usage needs to be added to @lookupDirectName... - 05:52 PM Bug #4741: RUN statement with a path to a procedure that does not have any extension fails to be ...
- Constantin asked:
Roger, rename @run-noext-victim.p@ to @run-noext-victim.k.p@ and do a @RUN run-noext-victim.k@. ... - 05:49 PM Bug #4741: RUN statement with a path to a procedure that does not have any extension fails to be ...
- There is an issue about finding an external procedure that is not passed to @RUN@ with an extension. I added this tes...
- 05:45 PM Bug #4741 (Closed): RUN statement with a path to a procedure that does not have any extension fai...
- 12:56 PM Bug #4734: Invalid string to date conversion for non-"mm/dd/yyyy" format
- Which FWD branch/revision?
- 12:20 PM Bug #4734: Invalid string to date conversion for non-"mm/dd/yyyy" format
- Testcase:...
- 12:12 PM Bug #4734 (Closed): Invalid string to date conversion for non-"mm/dd/yyyy" format
06/30/2020
- 11:11 AM Feature #4384: Builtin OO Implementation
- Marian, I think this is your change, right?...
06/25/2020
- 04:00 AM Feature #4384: Builtin OO Implementation
- We have some issues with OO named events, one of the tests does not pass conversion: @oo/openedge/net/http/filter/aut...
06/23/2020
- 03:24 PM Feature #3753: I18N additions
- Some things we've found and tried to fix soo far while implementing OO base classes...
- codepage conversion support... - 02:45 PM Feature #4384: Builtin OO Implementation
- Just making a note so don't forget about it, there is an issue with destructors when there is an error thrown from a ...
- 02:41 PM Feature #3855: implement equivalent support for REST (classic appserver, PASOE REST and WEB trans...
- Marian Edu wrote:
> Constantin, do you still need those extra tests for REST? I'm having troubles getting the deploy... - 02:02 PM Feature #3855: implement equivalent support for REST (classic appserver, PASOE REST and WEB trans...
- Greg Shah wrote:
> Task branch 4231b has been merged to trunk as revision 11347.
Constantin, do you still need th...
06/20/2020
- 12:10 PM Support #4657: memory overhead from preloading classes with LegacySignature
- Task branch 4231b has been merged to trunk as revision 11347.
- 12:00 PM Feature #4395 (Closed): add support for KEEP-MESSAGES option
- Task branch 4231b has been merged to trunk as revision 11347.
- 11:59 AM Feature #4162 (Closed): enhance existing SESSION:STARTUP-PARAMETERS support to honor -ininame value
- Task branch 4231b has been merged to trunk as revision 11347.
- 11:58 AM Feature #3812 (Closed): additions to SESSION system-handle
- Task branch 4231b has been merged to trunk as revision 11347.
- 11:58 AM Feature #4381 (Closed): implement LIBRARY() and MEMBER() built-in functions
- Task branch 4231b has been merged to trunk as revision 11347.
- 11:55 AM Feature #3855: implement equivalent support for REST (classic appserver, PASOE REST and WEB trans...
- Task branch 4231b has been merged to trunk as revision 11347.
- 11:55 AM Feature #3854: update appserver support with PASOE features
- Task branch 4231b has been merged to trunk as revision 11347.
- 11:54 AM Feature #3310: add support for the equivalent of the OpenEdge Web Services Adapter (and ProxyGen)...
- Task branch 4231b has been merged to trunk as revision 11347.
- 11:54 AM Bug #4602: fixes for OO 4GL and structured error handling
- Task branch 4231b has been merged to trunk as revision 11347.
- 11:53 AM Bug #4355 (Closed): exception member of the CATCH block can be referenced after the block catchin...
- Task branch 4231b has been merged to trunk as revision 11347.
- 11:53 AM Feature #4354: add GET-CLASS() function support
- Task branch 4231b has been merged to trunk as revision 11347.
- 11:53 AM Feature #4349 (Closed): add support for 4GL ENUM
- Task branch 4231b has been merged to trunk as revision 11347.
06/18/2020
- 07:46 AM Feature #4384: Builtin OO Implementation
- > Actually the offending one was org.aspectj.org.eclipse.jdt.internal.formatter.linewrap, if we need to add some extr...
- 07:29 AM Feature #4384: Builtin OO Implementation
- Greg Shah wrote:
> I've merged all the changes from 4384c (revisions 11569 through 11579) into 4231b revision 11606.... - 06:39 AM Bug #4682: modify FILE-INFO processing to honor searches for 4GL programs
- > To modify the Possenet, we'd be creating an offshoot that we would need to document. I believe it's best to utilize...
06/17/2020
- 06:40 PM Bug #4682: modify FILE-INFO processing to honor searches for 4GL programs
- Greg Shah wrote:
> Yes, but in FWD we have no such thing. I was not suggesting that we implement a "fake" procedure... - 06:00 PM Bug #4682: modify FILE-INFO processing to honor searches for 4GL programs
- Yes, but in FWD we have no such thing. I was not suggesting that we implement a "fake" procedure library result.
... - 05:50 PM Bug #4682: modify FILE-INFO processing to honor searches for 4GL programs
- More info related to the 4GL's behavior. It indicates we can proceed.
I was able to position a procedure library i... - 05:34 PM Bug #4682: modify FILE-INFO processing to honor searches for 4GL programs
- Greg Shah wrote:
> For a @.r@ file that is part of the application, there is no procedure library involved. For a p... - 04:12 PM Bug #4682: modify FILE-INFO processing to honor searches for 4GL programs
- For a @.r@ file that is part of the application, there is no procedure library involved. For a procedure that is a m...
- 04:04 PM Bug #4682: modify FILE-INFO processing to honor searches for 4GL programs
- The code in @adm2/containr.p@ does not specifically perform a @LIBRARY@ call, prior to the code snippet that we are a...
06/16/2020
- 07:49 PM Feature #4162 (WIP): enhance existing SESSION:STARTUP-PARAMETERS support to honor -ininame value
- Ready for test.
- 04:43 PM Bug #4682: modify FILE-INFO processing to honor searches for 4GL programs
- There is a common pattern in 4GL code that is used for "security". The idea is that the code will use some form of f...
- 04:34 PM Bug #4682 (Closed): modify FILE-INFO processing to honor searches for 4GL programs
06/15/2020
- 01:03 PM Feature #4162: enhance existing SESSION:STARTUP-PARAMETERS support to honor -ininame value
- Roger Borrello wrote:
> Is #4391 basically additional parsing in the same manner as this task?
Yes. - 10:54 AM Feature #4162: enhance existing SESSION:STARTUP-PARAMETERS support to honor -ininame value
- Is #4391 basically additional parsing in the same manner as this task?
- 10:52 AM Feature #4162: enhance existing SESSION:STARTUP-PARAMETERS support to honor -ininame value
- Changes to support @-ininame@ are checked into *4231b-11608* (@LegacyCLI.java@). Testcases indicated there should be ...
- 09:53 AM Feature #4162: enhance existing SESSION:STARTUP-PARAMETERS support to honor -ininame value
- Roger Borrello wrote:
> Ovidiu, you had made changes to @ClientCore@ in 2014 to emulate the @-ininame@ command-line ... - 09:53 AM Feature #4162: enhance existing SESSION:STARTUP-PARAMETERS support to honor -ininame value
- Ovidiu, you had made changes to @ClientCore@ in 2014 to emulate the @-ininame@ command-line parameter. Is there any c...
Also available in: Atom