Activity
From 09/18/2018 to 10/17/2018
10/17/2018
- 09:46 AM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- I think your examples are *not* showing direct memory usage.
From #3741-21:
> Another example is this: var-type... - 05:18 AM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- My plan at this time is this:
* implement the infrastructure to make everything working
* if there is difference be... - 03:08 AM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Greg Shah wrote:
> My first worry was that this was some kind of direct memory issue. For example, the value might ...
10/16/2018
- 06:42 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- My first worry was that this was some kind of direct memory issue. For example, the value might be passed as a memor...
- 03:24 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- There is some weird stuff with OUTPUT/INPUT-OUTPUT parameters, when the data-type specified at @SET-PARAMETER@ and th...
- 12:41 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Greg Shah wrote:
> > This will require some refactoring of the NativeInvoker APIs, to access it directly.
>
> I ... - 12:13 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- > it may make sense to have this started for the CALL handle
Agreed, go with this.
> This will require some re... - 12:07 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Greg, something related to ControlFlowOps: some time ago I had a thought of using a builder approach for invoking thi...
10/15/2018
- 06:13 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Greg Shah wrote:
> Constantin Asofiei wrote:
> > Open issues which will be left after everything else is working or... - 06:10 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Constantin Asofiei wrote:
> Open issues which will be left after everything else is working or postponed:
> * runti... - 05:08 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Open issues which will be left after everything else is working or postponed:
* runtime for @PROCEDURE-TYPE@ and @TH...
10/04/2018
- 06:08 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- I'm OK with hard coding the return values, however that does mean we'll have extra maintenance over time when Progres...
- 06:05 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- > Also, list-set-attrs for a call handle gives a memory violation error in 4GL.
Of course it does. :)
We won't ... - 06:00 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- OTOH, I think we should hard-code the values returned by these @list-query-attrs@ and @list-set-attrs@ builtin functi...
- 05:56 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Greg Shah wrote:
> For this POC we also need the built-in functions @LIST-QUERY-ATTRS()@ and @LIST-SET-ATTRS()@. It... - 05:54 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- For this POC we also need the built-in functions @LIST-QUERY-ATTRS()@ and @LIST-SET-ATTRS()@. It seems pretty close ...
- 05:52 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Yes, please add them now.
- 05:46 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- These attributes are not supported at parse time in FWD; they are all related to 'Invoking a Windows DLL routine or a...
- 05:37 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Created task branch 3741a from trunk rev 11285.
- 05:07 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Greg Shah wrote:
> Please take a look at @ProgressAst.keyword()@ and @ProgressAst.keywordAll()@. Is this what you a... - 04:38 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- Please take a look at @ProgressAst.keyword()@ and @ProgressAst.keywordAll()@. Is this what you are looking for?
- 04:30 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- For handle attributes and methods, there's interesting stuff, too:
* there is a kind of runtime-validation of the gi... - 03:44 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- I think parameter passing/validation will be one of the complex parts. 4GL has a validation done at the @set-paramete...
- 03:17 PM Feature #3741 (WIP): implement complete support for the CALL object handle and related attributes...
- 01:11 PM Feature #3741: implement complete support for the CALL object handle and related attributes and m...
- The application POC which we are working on uses @CREATE CALL@ and a pretty complete set of the attributes and method...
- 01:10 PM Feature #3741 (Closed): implement complete support for the CALL object handle and related attribu...
Also available in: Atom