Activity
From 11/19/2018 to 12/18/2018
12/18/2018
- 04:52 PM Feature #3751: implement support for OO 4GL and structured error handling
- FYI, this also eliminates the cases where that extra casting broke the converted code so it is good from that perspec...
- 04:51 PM Feature #3751: implement support for OO 4GL and structured error handling
- Ovidiu Maxiniuc wrote:
> Greg Shah wrote:
> > Revision 11380 has this change in @oo_calls.rules@:
> > [...]
> > I... - 03:55 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> Revision 11380 has this change in @oo_calls.rules@:
> [...]
> It definitely breaks some of my t... - 03:50 PM Feature #3751: implement support for OO 4GL and structured error handling
- Revision 11380 has this change in @oo_calls.rules@:...
- 01:05 PM Feature #3751: implement support for OO 4GL and structured error handling
- Revision 11376:
Fix for OBJECT_INVOCATION that has a first child of OO_METH_*. This is an unqualified method refer... - 11:03 AM Feature #3751: implement support for OO 4GL and structured error handling
- Revision 11371:
Fixes to have access mode and static qualifier emit properly for properties. The backing var for ... - 08:24 AM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> Greg, if you manage to decouple the dependency on "filenames_to_java_classnames" (which ... - 08:23 AM Feature #3751: implement support for OO 4GL and structured error handling
- *GES: Solved*
Right now I'm still working on the wrapping of method call parms. I can put that on hold to work on... - 08:20 AM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> Ovidiu, these legacy classes are used in our project and we need Java equivalents:
OK, ... - 08:16 AM Feature #3751: implement support for OO 4GL and structured error handling
- Responding here instead of #3750 because it is OO related.
> if we are in an ASSIGN statement and a property with ... - 08:06 AM Feature #3751: implement support for OO 4GL and structured error handling
- Ovidiu, these legacy classes are used in our project and we need Java equivalents:...
12/17/2018
- 05:44 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> Constantin Asofiei wrote:
> > 3750a rev 11369 fixes some var/class-event reference problems when... - 05:30 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg, if you manage to decouple the dependency on "filenames_to_java_classnames" (which prohibits CB to be ran on a s...
- 05:24 PM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> 3750a rev 11369 fixes some var/class-event reference problems when the definition is in ... - 05:12 PM Feature #3751: implement support for OO 4GL and structured error handling
- 3750a rev 11369 fixes some var/class-event reference problems when the definition is in a super-class. Please review...
- 04:24 PM Feature #3751: implement support for OO 4GL and structured error handling
- There are some issues with incorrect @tempidx@ for non-local var/class-event access, if the definition is in a super-...
- 03:55 PM Feature #3751: implement support for OO 4GL and structured error handling
- Revision 11368 includes fixes for:
* length-of contents in extent properties
* indexed getter return type
Ther... - 03:51 PM Feature #3751: implement support for OO 4GL and structured error handling
- You're right, that is the issue. Thanks!
- 03:48 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> The code for extent property getters is failing with:
>
> [...]
>
> The converted code:
> ... - 03:18 PM Feature #3751: implement support for OO 4GL and structured error handling
- The code for extent property getters is failing with:...
- 02:50 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> Constantin: Could you please review this change? The @HERE?@ comments are the places that I chan... - 02:20 PM Feature #3751: implement support for OO 4GL and structured error handling
- Revision 11366:
Fix for initializers created and stored in the depot on one program which are then pulled out of t... - 02:18 PM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> Ovidiu Maxiniuc wrote:
> > ((F3757)instance.ref()).v3.assign(new integer(456));
> I as... - 01:33 PM Feature #3751: implement support for OO 4GL and structured error handling
- I'm working on the following issues:
1. The unexpected/unrelated var initializers that appear in @oo/ComplexInterf... - 12:53 PM Feature #3751: implement support for OO 4GL and structured error handling
- The @CB@ phase failed with a access-mode problem for class events after ~150 minutes, in the code conversion part.
... - 10:58 AM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> Constantin Asofiei wrote:
> > I'm looking into @oldtype@, is a parser problem, as I men... - 10:55 AM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> Ovidiu Maxiniuc wrote:
> > The conversion stops in @assignments.rules@ while attempting... - 10:37 AM Feature #3751: implement support for OO 4GL and structured error handling
- Other issues:
* @Instance = new TestClass().@ is not compiling
* if you have a member @v@ and do a @Instance:v = 0@... - 10:23 AM Feature #3751: implement support for OO 4GL and structured error handling
- Ovidiu Maxiniuc wrote:
> I have 2 alternatives that work:
> ((F3757)instance.ref()).v3.assign(new integer(456));
I... - 10:19 AM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> This and other issues are fixed in 11358 and 11360.
Not purposely, I tested the code ge... - 09:14 AM Feature #3751: implement support for OO 4GL and structured error handling
- Ovidiu Maxiniuc wrote:
> The conversion stops in @assignments.rules@ while attempting to convert to long/int the @ol... - 09:12 AM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> Where is this code located? In a class method/c'tor? If so then yes, local static membe... - 08:56 AM Feature #3751: implement support for OO 4GL and structured error handling
- Ovidiu Maxiniuc wrote:
> The generation of setters is fixed. Committed revision 11361.
>
> However, I added some ... - 08:41 AM Feature #3751: implement support for OO 4GL and structured error handling
- The generation of setters is fixed. Committed revision 11361.
However, I added some code to that from note-222 and... - 07:56 AM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> I'm looking into the conversion abend related to @ // Instance:v3 = 456.@ commented line... - 06:33 AM Feature #3751: implement support for OO 4GL and structured error handling
- I'm looking into the conversion abend related to @ // Instance:v3 = 456.@ commented line.
- 06:32 AM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> The getter/setter for properties having as type an OO class must have the proper generic... - 06:11 AM Feature #3751: implement support for OO 4GL and structured error handling
- Committed revision 11359.
Fixed covariance of generics for OO methods. Now the signature for ... - 06:04 AM Feature #3751: implement support for OO 4GL and structured error handling
- The getter/setter for properties having as type an OO class must have the proper generic set. Currently they are emi...
- 01:07 AM Feature #3751: implement support for OO 4GL and structured error handling
- In revision 11357, I've added the rewriting of the references (local and non-local) to properly call the 4 different ...
- 07:51 PM Feature #3751: implement support for OO 4GL and structured error handling
- So I finally was able to make the local chaining for class events work, too. Now it converts OK - what is not workin...
- 08:12 PM Feature #2135: implement COPY-LOB language statement
- Branch 3750a/11356 adds conversion support for DB_REF_NON_STATIC and POLY on either side of the copy, in combination ...
12/16/2018
- 06:50 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> I will keep working on this, but I'm worried that the @getAst()@ support is not working for non-l... - 06:37 PM Feature #3751: implement support for OO 4GL and structured error handling
- With r11353 the code changes as follows (see previous in note-124 and 193):...
- 06:23 PM Feature #3751: implement support for OO 4GL and structured error handling
- I did a quick check for non-local properties and although the refid is there, it fails to lookup the javaname. Have ...
- 06:03 PM Feature #3751: implement support for OO 4GL and structured error handling
- Revision 11352 adds the extra methods for extent properties length-of and the indeterminate resize.
I think proper... - 05:47 PM Feature #3751: implement support for OO 4GL and structured error handling
- Having something like this inside a OO method def:...
- 05:29 PM Feature #3751: implement support for OO 4GL and structured error handling
- This the refid is needed for non-local events, too - otherwise I can't find the event's javaname to be able to genera...
- 04:58 PM Feature #3751: implement support for OO 4GL and structured error handling
- > If you want it to be a static method call, then you need to emit the qualified class name and the method name toget...
- 04:57 PM Feature #3751: implement support for OO 4GL and structured error handling
- The tree looks correct.
The object chaining always matches the leftmost referent first (the @primary_expr@ in @cha... - 04:54 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> This is a "standalone" method call (no qualifier). I think the @upPath("ASSIGNMENT/EXPRESSION")@... - 04:48 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> I don't have a problem relying upon the refid approach for final resolution of the names by refer... - 04:45 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg, does this AST look right to you, for a @x:e1@ access for the class event @e1@?...
- 03:06 PM Feature #3751: implement support for OO 4GL and structured error handling
- In @oo_calls.rules@:...
- 02:00 PM Feature #3751: implement support for OO 4GL and structured error handling
- I don't have a problem relying upon the refid approach for final resolution of the names by references. This is the ...
- 01:40 PM Feature #3751: implement support for OO 4GL and structured error handling
- > The emitted methods for DEFINE EVENT will be:
The publish method when implemented, must be private.
For abst... - 01:36 PM Feature #3751: implement support for OO 4GL and structured error handling
- Revision 11350 has the following changes:
* Separated variables and methods into separate legacy name maps.
* M... - 01:12 PM Feature #3751: implement support for OO 4GL and structured error handling
- The emitted methods for @DEFINE EVENT@ will be:
* For interfaces:... - 01:09 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> We could add this to the data stored in @ConvertedClassName@ to allow resolving the temp-idx late... - 01:03 PM Feature #3751: implement support for OO 4GL and structured error handling
- We could add this to the data stored in @ConvertedClassName@ to allow resolving the temp-idx later.
I am deep into... - 12:48 PM Feature #3751: implement support for OO 4GL and structured error handling
- Ovidiu, In the end your per-folder failure can't be solved easily, as the non-local method call is from a different f...
- 11:44 AM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> Constantin Asofiei wrote:
> > @static@ mode is not working now - can you look at it, please?
> ... - 11:41 AM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> @static@ mode is not working now - can you look at it, please?
I guess you mean @stat... - 11:31 AM Feature #3751: implement support for OO 4GL and structured error handling
- @static@ mode is not working now - can you look at it, please?
- 11:24 AM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> I don't think the @new object<BaseObject>()@ is needed here. Shouldn't we just define @ObjectOps... - 11:22 AM Feature #3751: implement support for OO 4GL and structured error handling
- Looking closer @legacy2java@ is already reset in a while loop just after a new class is loaded. It is already OK. S...
- 11:20 AM Feature #3751: implement support for OO 4GL and structured error handling
- >> There is something else I don't understand about legacy2java. The map is global for the system, but I think it sho...
- 11:14 AM Feature #3751: implement support for OO 4GL and structured error handling
- ...
- 11:08 AM Feature #3751: implement support for OO 4GL and structured error handling
- With r11343, the branch 3750a should be able to handle FIELD_CLASS tokens.
Constructs like ... - 11:04 AM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> In the usage of @convert_member_name@ during @annotations_prep@, shouldn't we use a different @le... - 10:46 AM Feature #3751: implement support for OO 4GL and structured error handling
- There is something else I don't understand about @legacy2java@. The map is global for the system, but I think it sho...
- 10:43 AM Feature #3751: implement support for OO 4GL and structured error handling
- In the usage of @convert_member_name@ during @annotations_prep@, shouldn't we use a different @legacy2java@ map for v...
- 10:18 AM Feature #3751: implement support for OO 4GL and structured error handling
- The primary benefit I see is that it keeps intact the design approach of the original application. Future developmen...
- 10:10 AM Feature #3751: implement support for OO 4GL and structured error handling
- OTOH, a problem with method approach is the signature: the @PUBLISH@ can have POLY arguments, and this complicates th...
- 10:06 AM Feature #3751: implement support for OO 4GL and structured error handling
- > I understand, but this is enforced by 4GL at compile time - so the override event must match the abstract version f...
- 09:50 AM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> Events can be abstract. This "feature" of 4GL event support suggests we need to move to a purely ... - 09:37 AM Feature #3751: implement support for OO 4GL and structured error handling
- We need to confirm this, but the 4GL docs say that the publish can only ever be called from within the same defining ...
- 09:24 AM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> The proposed conversion is:
> * 4GL
> [...]
> * FWD:
> [...]
It is the most close... - 09:01 AM Feature #3751: implement support for OO 4GL and structured error handling
- The proposed conversion is:
* 4GL... - 06:46 AM Feature #3751: implement support for OO 4GL and structured error handling
- 3750a rev 11348 adds USING conversion support.
I'm taking @- DEFINE EVENT and the related features@ next. - 06:05 AM Feature #3751: implement support for OO 4GL and structured error handling
- 3750a rev 11347 adds conversion support for the CATCH statement. In the end there was no need for a @CATCH_BLOCK/BLO...
- 03:33 AM Feature #3751: implement support for OO 4GL and structured error handling
- 3750a rev 11345 added ON ... THROW support, 'UNDO, THROW' and BLOCK-LEVEL and ROUTINE-LEVEL stmts.
Now I'm working...
12/15/2018
- 06:47 PM Feature #3751: implement support for OO 4GL and structured error handling
- I committed the small change related to FIELD_CLASS. Revision 11343.
- 05:58 PM Feature #3751: implement support for OO 4GL and structured error handling
- Ovidiu Maxiniuc wrote:
> Constantin Asofiei wrote:
> > You might have caught a bad revision. Please update again, ... - 05:57 PM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> You might have caught a bad revision. Please update again, your test works for me.
Wel... - 05:52 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> Questions about the new early name conversion approach:
>
> * How do I move the method_def and... - 05:38 PM Feature #3751: implement support for OO 4GL and structured error handling
- Revision 11342 fixes the extent getter/setters. I still need to add the other extent helpers. I plan to postpone th...
- 05:33 PM Feature #3751: implement support for OO 4GL and structured error handling
- Questions about the new early name conversion approach:
* How do I move the method_def and property getter/setter ... - 05:31 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> So if an @extent@ annotation exists at all, it is always an extent, even if set to 0 or 1?
Actua... - 05:30 PM Feature #3751: implement support for OO 4GL and structured error handling
- @oo.ComplexImplements@ has regressed recently. It now generates @obj@ and @num@ references even though the class is ...
- 05:28 PM Feature #3751: implement support for OO 4GL and structured error handling
- So if an @extent@ annotation exists at all, it is always an extent, even if set to 0 or 1?
- 05:25 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> I see the issue, I'm not handling -1 as the extent annotation.
Exactly, @-1@ is for indetermin... - 05:23 PM Feature #3751: implement support for OO 4GL and structured error handling
- I see the issue, I'm not handling -1 as the extent annotation. If I see 0 or 1, can I assume it is scalar?
- 05:16 PM Feature #3751: implement support for OO 4GL and structured error handling
- When I remove that file, the conversion completes. I can see that the @PropertyHolderExtents.cls@ has proper subscri...
- 05:14 PM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> Please try cleaning your project first - your registry.xml might be obsolete.
Nevermind... - 05:07 PM Feature #3751: implement support for OO 4GL and structured error handling
- Please try cleaning your project first - your registry.xml might be obsolete.
- 05:03 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> My previous code was successfully emitting the subscript for the fixed case. I can't check the c... - 05:02 PM Feature #3751: implement support for OO 4GL and structured error handling
- My previous code was successfully emitting the subscript for the fixed case. I can't check the current code because ...
- 04:59 PM Feature #3751: implement support for OO 4GL and structured error handling
- Ovidiu Maxiniuc wrote:
> I commented out all code except:
> [...]
> This fails with:
> [...]
You might have caug... - 04:56 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> > I don't understand why the indexed getter returns an array for flag - shouldn't this return jus... - 04:52 PM Feature #3751: implement support for OO 4GL and structured error handling
- As I noted in #3751-132, I'm planning to add: @lengthOf<property_name>()@ and @resize<property_name>()@ methods to ha...
- 04:52 PM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> Ovidiu Maxiniuc wrote:
> > There is not much of a difference. I have both @builtin_clas... - 04:48 PM Feature #3751: implement support for OO 4GL and structured error handling
- Ovidiu Maxiniuc wrote:
> There is not much of a difference. I have both @builtin_classes.xml@ and @filenames_to_java... - 04:45 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> I'm also having an issue with the indeterminate extent properties in @oo/PropertyHolderExtents.cl... - 04:39 PM Feature #3751: implement support for OO 4GL and structured error handling
- The TRPL problem and the tempidx issues are fixed in 11340.
- 04:38 PM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> TRPL has a 'var leak' where the var defined in current scope is visible in a function ca... - 04:30 PM Feature #3751: implement support for OO 4GL and structured error handling
- Ovidiu Maxiniuc wrote:
> Constantin Asofiei wrote:
> > Also, please use rev 11336 of 3750a - this separates the fr... - 04:28 PM Feature #3751: implement support for OO 4GL and structured error handling
- TRPL has a 'var leak' where the var defined in current scope is visible in a function call, in some cases - see @hasT...
- 04:17 PM Feature #3751: implement support for OO 4GL and structured error handling
- There is some "weirdness" going on in @convert/variable_definitions.rules@. There is a location where we create a @r...
- 03:51 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> After integrating your recent changes, property conversion is broken again. The @classname@ anno... - 03:49 PM Feature #3751: implement support for OO 4GL and structured error handling
- Rev 11338 provides support for property getters and setters. It was a major PITA.
After integrating your recent c... - 03:04 PM Feature #3751: implement support for OO 4GL and structured error handling
- 3750a rev 11337 fixes refid annotations for OO variables references outside of defining class.
- 02:07 PM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> Ovidiu Maxiniuc wrote:
> > I need a bit of help configuring (I guess) my isolation work... - 01:57 PM Feature #3751: implement support for OO 4GL and structured error handling
- Ovidiu Maxiniuc wrote:
> I need a bit of help configuring (I guess) my isolation workspace with ABL OO class support... - 01:54 PM Feature #3751: implement support for OO 4GL and structured error handling
- I need a bit of help configuring (I guess) my isolation workspace with ABL OO class support. My @SymbolResolver@ can...
- 12:06 PM Feature #3751: implement support for OO 4GL and structured error handling
- The current phase of class var access and chaining is in 3750a rev 11335. I need to rework this to use the 'refid' a...
- 11:26 AM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> 3. Later, when we use a refid to obtain the node for a given var def, we need a helper that will ... - 10:41 AM Feature #3751: implement support for OO 4GL and structured error handling
- OK, I'll work on that next. What showed the refid problem was the extent class var references, outside of the defini...
- 10:39 AM Feature #3751: implement support for OO 4GL and structured error handling
- The refid is unique across the project. It can be used between files without an issue. However, I think to make thi...
- 10:29 AM Feature #3751: implement support for OO 4GL and structured error handling
- Greg, references to variables outside of the defining class should not be annotated with 'refid' (and this annotation...
- 08:10 AM Feature #3751: implement support for OO 4GL and structured error handling
- The class var access and chaining works; I need to finish the extent function and subscript dereferencing before comm...
- 03:36 AM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> > We need to fix the access modifiers for all class data members (variables, resources, etc) - ar... - 01:03 AM Feature #3751: implement support for OO 4GL and structured error handling
- > We need to fix the access modifiers for all class data members (variables, resources, etc) - are you taking care of...
- 01:03 AM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> Greg, there is some confusion (at least for me) regarding the @qualified@ annotation.
>... - 12:59 AM Feature #3751: implement support for OO 4GL and structured error handling
- Revision 11332 is the first part of the define property support. It is not done yet.
- 08:32 PM Feature #3751: implement support for OO 4GL and structured error handling
- An important note: at least for OO, the CB phase depends on some state determined by the F0 phase (class definitions/...
- 08:27 PM Feature #3751: implement support for OO 4GL and structured error handling
- I've managed to go around the @qualified@ annotation, but this still confuses me.
3750a rev 11331 has a mostly wor... - 08:13 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg, there is some confusion (at least for me) regarding the @qualified@ annotation.
* In some parts, for example a... - 07:05 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> ** Get the converted name (I hope to leverage your work there).
See the changes in 3750a rev 113... - 03:58 AM Feature #2135 (WIP): implement COPY-LOB language statement
- Task branch 3750a/11334 includes basic support for copying between all combinations of @CLOB@, @BLOB@, @longchar@, an...
12/14/2018
- 05:10 PM Feature #3751: implement support for OO 4GL and structured error handling
- The following testcases show the behavior of properties (except for the access control options):...
- 05:02 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> I agree your approach makes sense. I had to do this for the class names but didn't get to the re... - 04:57 PM Feature #3751: implement support for OO 4GL and structured error handling
- I'm not working on it. I'm writing up my plan for properties right now. As you will see shortly, I've got my hands ...
- 04:43 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg, are you working on annotating the ASTs which access methods or other members with their converted java name? B...
- 04:20 PM Feature #3751: implement support for OO 4GL and structured error handling
- > I will do it tomorrow.
Thank you! - 04:15 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> Code Review Task branch 3750a Revision 11328
>
> Nice work! I think you have the M0 part in a... - 04:11 PM Feature #3751: implement support for OO 4GL and structured error handling
- Code Review Task branch 3750a Revision 11328
Nice work! I think you have the M0 part in a good place. Do you fee... - 04:10 PM Feature #3751: implement support for OO 4GL and structured error handling
- Code Review Task branch 3750a Revision 11327
It is good.
In line 705 of @buffer_definitions.rules@, there is th... - 03:57 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> One thing to consider is that our @object@ wrapper is a generic. When one considers that @FIELD_... - 03:24 PM Feature #3751: implement support for OO 4GL and structured error handling
- 3750a rev 11327 :
* finishes the constructor/destructor support
* implicit initialization c'tor - our 'execute' met... - 01:52 PM Feature #3751: implement support for OO 4GL and structured error handling
- > > If I understand it correctly, it should be the same as we define now except we don't need any buffers.
> The b... - 01:46 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> If I understand it correctly, it should be the same as we define now except we don't need any buf... - 01:15 PM Feature #3751: implement support for OO 4GL and structured error handling
- If I understand it correctly, it should be the same as we define now except we don't need any buffers. The define st...
- 01:12 PM Feature #3751: implement support for OO 4GL and structured error handling
- I'm not removing the promotion, the thing here is that our var defs rules were dependent upon some values initializin...
- 01:10 PM Feature #3751: implement support for OO 4GL and structured error handling
- How do we treat the @temp-table@ defined at an interface?
- 12:54 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> For example, I had to make up for the lack of an @execute()@ method in classes by "faking" some i... - 12:52 PM Feature #3751: implement support for OO 4GL and structured error handling
- > part of object creation there will be a call to a __p1_Bar_execute__ method, which emulates an empty external progr...
- 12:47 PM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> A part with resource data members is code like @frame.openScope()@ - this needs to be em... - 12:26 PM Feature #3751: implement support for OO 4GL and structured error handling
- > but not sure about the default ? value
Object instances default to unknown value so this is consistent. Consid... - 12:24 PM Feature #3751: implement support for OO 4GL and structured error handling
- I'm responding to #3750-69 here so that all the @FIELD_CLASS@ information is in one place. See #3751-48 for some use...
- 12:21 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> Revision 11326 provides fixes to make interface definitions work properly.
> Ovidiu: Is the @FIE... - 11:51 AM Feature #3751: implement support for OO 4GL and structured error handling
- I'm taking SUPER and THIS-OBJECT, too.
- 11:05 AM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> Constantin: What are you working on right now? I think it is time to handle conversion of @OBJEC... - 10:39 AM Feature #3751: implement support for OO 4GL and structured error handling
- Revision 11326 provides fixes to make interface definitions work properly.
Ovidiu: Is the @FIELD_CLASS@ support co... - 05:35 AM Feature #3751: implement support for OO 4GL and structured error handling
- The constructor and destructor conversion is in 3750a rev 11323:
What's left here:
* implicit initialization c'tor ... - 05:00 AM Feature #3751: implement support for OO 4GL and structured error handling
- I'm working on what you mentioned in #3751-106. Note that the vars defined within a method are not scoped to it - I'...
- 11:33 PM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin: Everything I've been working on is checked in. Some thoughts:
1. To work on the non-var members, I re... - 10:58 PM Feature #3751: implement support for OO 4GL and structured error handling
- Revision 11322 provides fully functional method definition support.
12/13/2018
- 05:40 PM Feature #3751: implement support for OO 4GL and structured error handling
- Rev 11321 adds more method def support. It is almost working now. Method parameters are broken. I'm working on it.
- 05:06 PM Feature #3751: implement support for OO 4GL and structured error handling
- A part with resource data members is code like @frame.openScope()@ - this needs to be emitted I think in 'legacy defa...
- 04:29 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> In the interim, can you please look at data members that are not vars (buffers, frames...) in cla... - 03:22 PM Feature #3751: implement support for OO 4GL and structured error handling
- I'm about to have an implementation of methods pretty soon (at least in classes). At that time we can figure out the...
- 03:12 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> @isTopLevel@ excludes the class or interface body but @isTopLevelOrOO@ does not.
>
> Revision ... - 02:38 PM Feature #3751: implement support for OO 4GL and structured error handling
- I guess I should have said: we are deliberately excluding those in @isTopLevel@ because the places where it is being ...
- 02:37 PM Feature #3751: implement support for OO 4GL and structured error handling
- @isTopLevel@ excludes the class or interface body but @isTopLevelOrOO@ does not.
Revision 11319 adds more enableme... - 02:33 PM Feature #3751: implement support for OO 4GL and structured error handling
- What was the purpose to add @isTopLevelOrOO@ instead of just changing @isTopLevel@ to handle OO blocks, too?
- 02:15 PM Feature #3751: implement support for OO 4GL and structured error handling
- 3750a ref 11318 contains:
* Added CAST, DYNAMIC-CAST, DYNAMIC-NEW, NEW, TYPE-OF, VALID-OBJECT.
* Emit .class Java ... - 02:08 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> However, I agree that @CAST@ needs to return an @object@.
>
> But why not emit this for chaini... - 02:03 PM Feature #3751: implement support for OO 4GL and structured error handling
- However, I agree that @CAST@ needs to return an @object@.
But why not emit this for chaining: @ObjectOps.cast(o, c... - 02:02 PM Feature #3751: implement support for OO 4GL and structured error handling
- > OTOH, it can be emitted like @ObjectOps.cast(o, com.goldencode.testcases.p1.O1.class).m1();@ if its signature is @p...
- 01:59 PM Feature #3751: implement support for OO 4GL and structured error handling
- @CAST@ allows a construct like @cast(o, p1.O1):m1().@.
This needs to be converted to something like:... - 01:30 PM Feature #3751: implement support for OO 4GL and structured error handling
- We are excluding support for duck typing as a permanent restriction, so we don't need strings there.
@DYNAMIC-CA... - 01:16 PM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> Greg Shah wrote:
> > Can you think of any other case for indirect invocation?
> 4GL ha... - 01:11 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> Constantin Asofiei wrote:
> > @CLASS_NAME@ literals will emit as string literals with the legacy... - 01:11 PM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> @CLASS_NAME@ literals will emit as string literals with the legacy qualified class name ... - 01:01 PM Feature #3751: implement support for OO 4GL and structured error handling
- @CLASS_NAME@ literals will emit as string literals with the legacy qualified class name or Java full qualified name?
- 12:50 PM Feature #3751: implement support for OO 4GL and structured error handling
- > I think Progress.Lang.Class should be LegacyClass or something.
I like it. - 12:48 PM Feature #3751: implement support for OO 4GL and structured error handling
- Plus @CLASS_NAME@ literals.
- 12:48 PM Feature #3751: implement support for OO 4GL and structured error handling
- I'm adding these to my list:...
- 12:20 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> Can you think of any other case for indirect invocation?
4GL has reflection support via @Progres... - 12:19 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> Constantin Asofiei wrote:
> > Do you still want to use @BaseObject@ name for @Progress.Lang.Obje... - 12:17 PM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> Do you still want to use @BaseObject@ name for @Progress.Lang.Object@ class?
I wanted... - 12:16 PM Feature #3751: implement support for OO 4GL and structured error handling
- 3750a rev 11317:
* added DELETE OBJECT obj, SESSION:LAST/FIRST-OBJECT conversion support.
* reworked builtin clas... - 11:56 AM Feature #3751: implement support for OO 4GL and structured error handling
- Do you still want to use @BaseObject@ name for @Progress.Lang.Object@ class?
- 11:37 AM Feature #3751: implement support for OO 4GL and structured error handling
- > Also, I assume only stubs will be added for i.e. delete, nextSibling(), etc
Yes, this is OK. - 11:36 AM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> Eric Faulhaber wrote:
> > A minor thing, but... is there a reason this needs to be a su... - 11:36 AM Feature #3751: implement support for OO 4GL and structured error handling
- For normal expressions processing (object and class dereferencing), we are planning to use a direct method invocation...
- 11:35 AM Feature #3751: implement support for OO 4GL and structured error handling
- OO method calls and attribute access is not there yet, correct?
Also, I assume only stubs will be added for i.e. @... - 11:34 AM Feature #3751: implement support for OO 4GL and structured error handling
- Eric Faulhaber wrote:
> A minor thing, but... is there a reason this needs to be a sub-package of @util@? How about ... - 11:32 AM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> I'd just get rid of this package and use something like @com.goldencode.p2j.util.oo.lang... - 11:16 AM Feature #3751: implement support for OO 4GL and structured error handling
- 3750a rev 11316 is some intermediate changes for method definitions. They are not working yet, but I don't want our ...
- 11:15 AM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> Can we automate the @annotations_prep.rules@ step of registering the built-in classes?
... - 11:11 AM Feature #3751: implement support for OO 4GL and structured error handling
- Can we automate the @annotations_prep.rules@ step of registering the built-in classes?...
- 11:01 AM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> Is @Progress.Lang.Object@ skeleton required to be in the conversion list? I get this for... - 11:00 AM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> Is @Progress.Lang.Object@ skeleton required to be in the conversion list? I get this for... - 10:58 AM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> Do we already have a OO ops helper class? For @new@, @delete@, etc.
>
> If not, I'll ... - 10:57 AM Feature #3751: implement support for OO 4GL and structured error handling
- Is @Progress.Lang.Object@ skeleton required to be in the conversion list? I get this for a @def var o as Progress.Lan...
- 10:50 AM Feature #3751: implement support for OO 4GL and structured error handling
- Do we already have a OO ops helper class? For @new@, @delete@, etc.
If not, I'll add ObjectOps. - 10:44 AM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> This seems reasonable. One question: why is the package part needed? I'd rather decorate it wit... - 10:43 AM Feature #3751: implement support for OO 4GL and structured error handling
- > the constructors will not be Java constructors, but object initialization methods
Yes, this is my understanding ... - 10:39 AM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> I'm working on getting data members to emit properly. Then I am going to take method definitions... - 07:25 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> Functions even share the same namespace as internal procedures.
>
> Why do we need to disamb... - 07:03 PM Feature #3751: implement support for OO 4GL and structured error handling
- Since methods can't be in the same compilation unit with functions or procedures, there cannot be any naming conflict...
12/12/2018
- 06:49 PM Feature #3751: implement support for OO 4GL and structured error handling
- I also did confirm that internal procedures and user defined functions cannot be defined inside a class definition.
... - 06:46 PM Feature #3751: implement support for OO 4GL and structured error handling
- Triggers can be defined inside a class as shown by this example:...
- 10:52 PM Feature #3751: implement support for OO 4GL and structured error handling
- 3750a rev 11313 provides support for variables as data members in classes or interfaces.
12/11/2018
- 04:21 PM Feature #3751: implement support for OO 4GL and structured error handling
- I'm working on getting data members to emit properly. Then I am going to take method definitions.
Constantin: Aft... - 04:18 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> > Is anyone working on the conversion of FIELD_CLASS right now?
>
> I'm not.
>
> Constantin... - 04:16 PM Feature #3751: implement support for OO 4GL and structured error handling
- > Is anyone working on the conversion of FIELD_CLASS right now?
I'm not.
Constantin ? - 04:14 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> * Is there any reason to believe that the OO 4GL object instances are a kind of handle (other tha... - 04:07 PM Feature #3751: implement support for OO 4GL and structured error handling
- 3750a rev 11312 provides variable and parameter definition support for AS CLASS, LIKE VAR_CLASS and LIKE FIELD_CLASS....
- 03:25 PM Feature #3751: implement support for OO 4GL and structured error handling
- I'm working on var/parm defs right now. I've just checked in 3750a rev 11311 which is an early version of the @objec...
- 02:28 PM Feature #3751: implement support for OO 4GL and structured error handling
- Eric suggests using @object@ instead of @ObjectRef@. It is shorter and is in the same kind of lowercase format as th...
- 11:55 AM Feature #3751: implement support for OO 4GL and structured error handling
- I've been writing some testcases to explore unknown value, assignment and undo. In all of these areas, the behavior ...
12/10/2018
- 05:00 PM Feature #3751: implement support for OO 4GL and structured error handling
- The 4GL documentation for FIELD_CLASS states that it is only possible to make it @Progress.Lang.Object@. It turns ou...
- 10:04 AM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> I'm talking about the creation of the widget pool itself, not the registration of handle resource... - 09:36 AM Feature #3751: implement support for OO 4GL and structured error handling
- >> For the instance case, we can create it in the "constructor worker" method. For the class case, in a static intial...
12/09/2018
- 05:47 PM Feature #3751: implement support for OO 4GL and structured error handling
- 3750a revision 11307 adds support for @IMPLEMENTS@.
- 01:56 PM Feature #3751: implement support for OO 4GL and structured error handling
- 3750a revision 11306 is the first phase of conversion support for OO 4GL. This revision can properly convert empty c...
12/08/2018
- 02:54 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> Is there a different widget pool for each instance or is there a single widget pool for the class... - 12:36 PM Feature #3751: implement support for OO 4GL and structured error handling
- > Same, I think this is some compile-time augmentation for CREATE statements using static members.
Is there a dif...
12/07/2018
- 06:22 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> > And @USE-WIDGET-POOL@ - is this currently used?
>
> Sorry, it took some time to run the sear... - 04:46 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> * I assume that statics are not affected, only instance members. The 4GL doesn't allow accessing... - 04:28 PM Feature #3751: implement support for OO 4GL and structured error handling
- > Greg, we need to determine how we handle the same stuff with unknown object references, for normal var case. 4GL gi...
- 03:45 PM Feature #3751: implement support for OO 4GL and structured error handling
- > And @USE-WIDGET-POOL@ - is this currently used?
Sorry, it took some time to run the search across both projects.... - 03:29 PM Feature #3751: implement support for OO 4GL and structured error handling
- Direct field reference like @where tt.obj = ?@ or @where tt.obj <> ?@ does work.
But there is something interestin... - 02:55 PM Feature #3751: implement support for OO 4GL and structured error handling
- Eric Faulhaber wrote:
> If so, how is tt.obj.foo dereferenced? Is this the equivalent of a user-defined function, wh... - 02:18 PM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin, are there any limitations as to how a field of data type @class@ can be used in a WHERE clause? For insta...
- 02:10 PM Feature #3751: implement support for OO 4GL and structured error handling
- Something about widget definitions in a class (like @DEF BUTTON btn@) - in documentation there is a statement like 'C...
12/06/2018
- 02:33 PM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> * how do you plan to emit the 4GL c'tors? As a Java constructor, right?
And I just real... - 02:28 PM Feature #3751: implement support for OO 4GL and structured error handling
- About constructors and destructors:
* how do you plan to emit the 4GL c'tors? As a Java constructor, right?
* destr... - 01:06 PM Feature #3751: implement support for OO 4GL and structured error handling
- I think we can calculate this if I just add the fully qualified OO name to the @class-mapping@ node as an @ooname@ at...
- 12:41 PM Feature #3751: implement support for OO 4GL and structured error handling
- I've been assuming that we will need the conversion name mapping anyway for things like @DYNAMIC-NEW@. I was thinkin...
- 12:34 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> My idea is that at parsing time, we have resolved the 4GL fully qualified names to some actual un... - 10:36 AM Feature #3751: implement support for OO 4GL and structured error handling
- I'm working on the resolution of the converted Java class name information (simple class name, package name and fully...
- 10:00 AM Feature #3751: implement support for OO 4GL and structured error handling
- Branch 3750a revision 11302 includes these changes:
* Added reports for constructors, destructors and duplicate fu...
12/05/2018
- 06:03 PM Feature #3751: implement support for OO 4GL and structured error handling
- Good results so far. Please check in your testcases to @testcases/uast/oo/@.
Next questions:
5. Please conside... - 05:15 PM Feature #3751: implement support for OO 4GL and structured error handling
- Leaving duck typing aside, and looking through the JVM specs, I can't find other issues at this time.
This comment... - 03:58 PM Feature #3751: implement support for OO 4GL and structured error handling
- > JVM specs don't guarantee which tread will execute the finalize() method - and if the DESTRUCTOR contains 4GL logic...
- 03:39 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> I think so. You aren't supposed to be able to execute it directly and it only gets executed when... - 03:33 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> > in Java you can't hide an instance method via a static method, but you can in 4GL.
>
> Did y... - 03:32 PM Feature #3751: implement support for OO 4GL and structured error handling
- Constantin Asofiei wrote:
> Another issue with using Java inheritance: in Java, you can't reduce the visibility of a... - 03:29 PM Feature #3751: implement support for OO 4GL and structured error handling
- > You mean without using a dynamic proxy? The problem I can think of is the EXTENT parameters - there is some validat...
- 03:26 PM Feature #3751: implement support for OO 4GL and structured error handling
- > in Java you can't hide an instance method via a static method, but you can in 4GL.
Did you find this via testing... - 03:26 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> Is there any reason that a method call with non-POLY arguments can't be directly dispatched?
You... - 03:20 PM Feature #3751: implement support for OO 4GL and structured error handling
- And there is this "gem" (from the 4GL docs):
"On a state-reset AppServer, a given AppServer agent begins a fresh A... - 03:01 PM Feature #3751: implement support for OO 4GL and structured error handling
- Also in Java you can't hide an instance method via a static method, but you can in 4GL.
LE: this was tested incorr... - 02:55 PM Feature #3751: implement support for OO 4GL and structured error handling
- Another issue with using Java inheritance: in Java, you can't reduce the visibility of a member, just upgrade it. In...
- 02:42 PM Feature #3751: implement support for OO 4GL and structured error handling
- > I was thinking we could do a mode where, if a project is not using duck-typing, we rely on Java inheritance for con...
- 02:31 PM Feature #3751: implement support for OO 4GL and structured error handling
- I was thinking we could do a mode where, if a project is not using duck-typing, we rely on Java inheritance for conve...
- 01:58 PM Feature #3751: implement support for OO 4GL and structured error handling
- Use @string(THIS-OBJECT)@ (or @string(ooVar)@) to determine the handle ID (this is suffixed to the class name, like @...
- 01:41 PM Feature #3751: implement support for OO 4GL and structured error handling
- Greg Shah wrote:
> > the limitations introduced by duck typing I think will not allow us to use Java inheritance, wh... - 01:36 PM Feature #3751: implement support for OO 4GL and structured error handling
- > the limitations introduced by duck typing I think will not allow us to use Java inheritance, when emulating the 4GL...
- 01:24 PM Feature #3751: implement support for OO 4GL and structured error handling
- 4. About @static@ constructors. 4GL states:
> STATIC specifies a static constructor that executes exactly once in an... - 01:17 PM Feature #3751: implement support for OO 4GL and structured error handling
- I'm posting our duck typing example here so that readers can see the full context of the discussion.
@duck_typing....
12/04/2018
- 05:12 PM Feature #3755 (Closed): DEBUGGER system handle stubs
- Code Review Task Branch 3750a Revision 11300
I'm good with the changes.
In the future, I would like to avoid th... - 01:51 PM Feature #3755 (Review): DEBUGGER system handle stubs
- 01:51 PM Feature #3755 (WIP): DEBUGGER system handle stubs
- DEBUGGER support - full conversion and stubbed runtime - is in 3750a rev 11294.
- 03:13 PM Feature #3753: I18N additions
- A note to check: editor with LONGCHAR value, having a non-default codepage.
- 02:35 PM Feature #3753: I18N additions
- The conversion issues for this task (phase 1) are solved in 3750a rev 11297.
- 02:07 PM Feature #3756 (WIP): minor modifications for SESSION system handle support
- The conversion problems in this task are solved in 3750a rev 11295: adds SESSION:V6DISPLAY conversion and get/set run...
12/03/2018
- 09:08 AM Feature #3752 (Closed): CLIENT-PRINCIPAL resource and other security features
- The remainder of the CLIENT-PRINCIPAL support will be implemented in #3810.
- 08:53 AM Feature #3752: CLIENT-PRINCIPAL resource and other security features
- 3752a was merged to trunk rev 11293 and archived.
> Added runtime/conversion support for SET-DB-CLIENT, GET-DB-CLI...
12/01/2018
- 07:50 AM Feature #3752: CLIENT-PRINCIPAL resource and other security features
- Please merge to trunk.
11/30/2018
- 04:23 PM Feature #3752: CLIENT-PRINCIPAL resource and other security features
- Conversion testing of 3752a rev 11297 passed.
- 02:05 PM Feature #3752: CLIENT-PRINCIPAL resource and other security features
- 3752a rev 11297 fixes the review issues.
I'm doing conversion testing next. - 01:49 PM Feature #3752: CLIENT-PRINCIPAL resource and other security features
- Greg Shah wrote:
> > If the name is invalid, I'll throw an exception, as we can't use the default DB.
>
> OK, as ... - 01:45 PM Feature #3752: CLIENT-PRINCIPAL resource and other security features
- > If the name is invalid, I'll throw an exception, as we can't use the default DB.
OK, as long as the NPE does not... - 01:43 PM Feature #3752: CLIENT-PRINCIPAL resource and other security features
- Greg Shah wrote:
> 1. In @ConnectionManager.getDbClient()/setDbClient()@, the use of @cm.getLDBName(dbName).toLowerC... - 11:15 AM Feature #3752: CLIENT-PRINCIPAL resource and other security features
- I don't think this needs runtime testing. If it passes conversion testing for ChUI, it can be merged to trunk.
- 11:14 AM Feature #3752: CLIENT-PRINCIPAL resource and other security features
- Code Review Task Branch 3752a Revision 11295
The result is very good. I've only found some minor issues:
1. In...
11/29/2018
- 02:36 PM Feature #3753 (WIP): I18N additions
11/28/2018
- 12:46 PM Feature #3752: CLIENT-PRINCIPAL resource and other security features
- Please review 3752a rev 11295 - it contains the changes required for the current POC.
11/26/2018
- 12:58 PM Feature #3817: create resource bundles from string literals and implement optional support for se...
- This is meant to be a Java-native replacement for the ability to swap translated string literals at runtime.
+Back... - 12:21 PM Feature #3817 (Closed): create resource bundles from string literals and implement optional suppo...
11/25/2018
- 11:05 AM Feature #3753: I18N additions
- Implement these for Phase 2 (main project):
* generalized CONVERT option support (e.g. not just INPUT but also use... - 10:36 AM Feature #2135: implement COPY-LOB language statement
- As phase 3 of development, the following will all be needed:...
- 09:23 AM Feature #3812: additions to SESSION system-handle
- +Attributes+
* CURRENT-REQUEST-INFO
* LOCAL-VERSION-INFO
* SERVER-CONNECTION-BOUND-REQUEST
* ICFPARAMETER
* CO... - 09:19 AM Feature #3812 (Closed): additions to SESSION system-handle
- 08:21 AM Feature #3810: SECURITY-POLICY and other security features
- Implement support for the following:
+SECURITY-POLICY resource+
* SECURITY-POLICY system handle
* attributes
... - 07:41 AM Feature #3810 (Closed): SECURITY-POLICY and other security features
11/19/2018
- 03:01 PM Feature #3752: CLIENT-PRINCIPAL resource and other security features
- Something else: the @_oeusertable@ and any other domain type allows any user ID to be specified, even if it does not ...
- 01:05 PM Feature #3752: CLIENT-PRINCIPAL resource and other security features
- Greg Shah wrote:
> Is the @_oslocal@ approach using something like PAM or does it just rely upon the user being alre... - 01:02 PM Feature #3752: CLIENT-PRINCIPAL resource and other security features
- Is the @_oslocal@ approach using something like PAM or does it just rely upon the user being already logged in?
- 12:50 PM Feature #3752: CLIENT-PRINCIPAL resource and other security features
- These metadata tables define the domains and the domain types:...
Also available in: Atom