Activity
From 02/01/2013 to 03/02/2013
03/02/2013
- 06:11 PM Feature #2074: add CAN-QUERY() and CAN-SET() support
- The ges_upd20130302b.zip passed conversion testing and checked in as bzr revision 10233.
- 05:40 PM Feature #2074: add CAN-QUERY() and CAN-SET() support
- This code provides the conversion support for these builtin functions. It also stubs out the methods in HandleOps. ...
- 05:38 PM Feature #2074 (Closed): add CAN-QUERY() and CAN-SET() support
- 08:15 PM Feature #2050: ATTR_POLY/METH_POLY used as rvalue or in expressions
- Passed conversion testing and checked in as bzr revision 10230.
03/01/2013
- 05:17 PM Feature #2050: ATTR_POLY/METH_POLY used as rvalue or in expressions
- This passed testing, but in further processing of the customer code, another (virtually identical) NPE was encountere...
- 03:29 PM Feature #2050: ATTR_POLY/METH_POLY used as rvalue or in expressions
- Attached is the fix (and testcase updates) for this case. Based on testing in the 4GL, one can indeed have the retur...
- 02:10 PM Bug #2070: BlockManager Action disambiguation
- Code Feedback:
In regard to the converted class names, there are several problems that have to be addressed:
1.... - 12:20 PM Bug #2070: BlockManager Action disambiguation
- I haven't reviewed your update, but yes, that approach is OK. I was responding to Constantin's idea about maintainin...
- 12:14 PM Bug #2070: BlockManager Action disambiguation
- I used isDMOInterface(String) in the defined function usedClassName (core_conversion.xml) from the proposed update to...
- 12:09 PM Bug #2070: BlockManager Action disambiguation
- BTW, if this is called more than once, we will want to optimize it, because it copies large sets of strings.
- 12:07 PM Bug #2070: BlockManager Action disambiguation
- ...and the attachment.
- 12:06 PM Bug #2070: BlockManager Action disambiguation
- Here, give this a try. Register P2OAccessWorker in TRPL and call @getAllDMOInterfaceNames()@ to return a set of all ...
- 11:58 AM Bug #2070: BlockManager Action disambiguation
- Added proposed update
- 11:31 AM Bug #2070: BlockManager Action disambiguation
- Greg, do we have a way of knowing if a certain name is for a converted class name (associated with the external progr...
- 11:26 AM Bug #2070: BlockManager Action disambiguation
- Please look at the com.goldencode.p2j.schema.P2OAccessWorker as a better solution than manually parsing the dmo_index...
- 11:22 AM Bug #2070: BlockManager Action disambiguation
- Please do the following and re-upload:
# rename dmoUsedNames to usedClassNames (idea is, to save all generated class... - 11:07 AM Bug #2070: BlockManager Action disambiguation
- Added proposed update. Solution was to parse the dmo_index.xml file and retrieve the existing dmo names in a global H...
02/28/2013
- 06:48 PM Bug #2056 (Closed): null value for an annotation while persisting the AST
- 06:47 PM Bug #2056: null value for an annotation while persisting the AST
- Passed conversion testing and is checked into bzr as revision 10226.
- 05:31 PM Bug #2056: null value for an annotation while persisting the AST
- OK, some findings:
1. Generally, @@@ base-field can only be used in a DISPLAY stmt and in the column_spec of a DEF... - 06:10 PM Feature #2063: Support negative numbers defined with the "-" on the right side
- The lexer cannot easily change its behavior in response to feedback from the parser. This is a core limitation of AN...
- 04:30 PM Feature #2063: Support negative numbers defined with the "-" on the right side
- We have a case where the @999.99-@ literal is converted to @new date("999.99-")@ instead of decimal:...
- 02:51 PM Bug #2070: BlockManager Action disambiguation
- Keep in mind that BUFFER_SCOPE is for DMOs beeing used by the current program, and not all the existing DMOs. I think...
- 02:35 PM Bug #2070: BlockManager Action disambiguation
- Can the "classname" annotation of BUFFER_SCOPE be used safely to get that checked?
- 02:12 PM Bug #2070: BlockManager Action disambiguation
- Costin, looks like we need another check: if there is a DMO class with the Action name, then qualify Action with Bloc...
- 11:47 AM Bug #2070: BlockManager Action disambiguation
- This is fine for now. Ultimately, we will need to do this on a more global scale for all names. Please get it conver...
- 11:39 AM Bug #2070: BlockManager Action disambiguation
- Added proposed update
- 10:43 AM Bug #2070: BlockManager Action disambiguation
- Do you think it's better to replace Action.<enum_val> with BlockManager.Action.<enum_val> allways or check file name ...
- 10:40 AM Bug #2070: BlockManager Action disambiguation
- When we have a progress file named action and it contains a block which will emit a reference to the Action enum of t...
- 10:35 AM Bug #2070 (Closed): BlockManager Action disambiguation
- 11:02 AM Bug #2069: Accumulator temp table field disambiguation
- After the note 75 in the 1985, looks like this is a true buffer disambiguation problem, which can be duplicated using...
- 06:09 AM Bug #2069: Accumulator temp table field disambiguation
- For the following testcase we define a temp table fit a field name that already exists in a permanent table and use i...
- 05:58 AM Bug #2069 (Closed): Accumulator temp table field disambiguation
- If we create a temp table with a field name that coincides with a field from an existent permanent table and use accu...
02/27/2013
- 06:13 PM Feature #2050: ATTR_POLY/METH_POLY used as rvalue or in expressions
- A new context analysis problem has been found in #1985 (see note 63). The 2nd operand of the PLUS is a FIELD_DEC typ...
- 05:43 PM Bug #2056: null value for an annotation while persisting the AST
- One other point: I think if we get the parser right, the downstream processing may be much simpler. Today, we have t...
- 05:41 PM Bug #2056: null value for an annotation while persisting the AST
- After looking at this in detail, it is clear that this is something that I need to work on. Both of you should work ...
- 10:32 AM Bug #2056: null value for an annotation while persisting the AST
- This code works in P2J:...
- 09:47 AM Bug #2056: null value for an annotation while persisting the AST
- I was trying to force the rules to see the var definition hidden in the format_phrase node, and emit widget + var for...
- 09:36 AM Bug #2056: null value for an annotation while persisting the AST
- I can help with this.
Constantin: do you have any other findings to report?
We do support @-base fields alrea... - 12:14 PM Bug #2065: ambiguity in date/decimal literals that is not handled properly by the ProgressLexer
- For details, please see notes 6 and 7 of #2063.
- 12:13 PM Bug #2065 (Closed): ambiguity in date/decimal literals that is not handled properly by the Progre...
- 12:12 PM Feature #2063 (Closed): Support negative numbers defined with the "-" on the right side
- 11:39 AM Feature #2063: Support negative numbers defined with the "-" on the right side
- Commited to bzr as revision number 10220.
- 11:17 AM Feature #2063: Support negative numbers defined with the "-" on the right side
- Has passed conversion regression testing (no changes in generated sources), please check in and distribute.
- 09:30 AM Feature #2063: Support negative numbers defined with the "-" on the right side
- I'm OK with it. Put it through conversion testing.
- 09:28 AM Feature #2063: Support negative numbers defined with the "-" on the right side
- Added proposed update
- 09:08 AM Feature #2063: Support negative numbers defined with the "-" on the right side
- The coding changes look OK. Moving the sign to the left was what I was going to propose. Make sure you remove the e...
- 09:06 AM Feature #2063: Support negative numbers defined with the "-" on the right side
- We must be very careful here....
- 08:18 AM Feature #2063: Support negative numbers defined with the "-" on the right side
- Please test with these cases too:...
- 08:02 AM Feature #2063: Support negative numbers defined with the "-" on the right side
- Added proposed update which corrects the assignment.
- 06:44 AM Feature #2063: Support negative numbers defined with the "-" on the right side
- Update looks good, this is going through conversion regression testing now.
- 06:13 AM Feature #2063: Support negative numbers defined with the "-" on the right side
- This update fixes conversion side but there is still work to do to have the correct value set.
- 04:37 AM Feature #2063: Support negative numbers defined with the "-" on the right side
- Statements like: ...
- 04:31 AM Feature #2063 (Closed): Support negative numbers defined with the "-" on the right side
- 10:35 AM Bug #2061: unreachable code is too aggressive when shared vars are used
- Greg Shah wrote:
> Everything looks good here, except the copyright dates in the new ruleset. You can check in a fi... - 09:09 AM Bug #2061 (Closed): unreachable code is too aggressive when shared vars are used
- Everything looks good here, except the copyright dates in the new ruleset. You can check in a fix without any furthe...
- 08:00 AM Bug #2061 (Review): unreachable code is too aggressive when shared vars are used
- This has passed conversion regression testing on MAJIC, no resurfaced dead-code.
Committed to bzr revision 10218. - 06:28 AM Bug #2061: unreachable code is too aggressive when shared vars are used
- I'm reposting cause I had a left behind printfln.
- 06:11 AM Bug #2061: unreachable code is too aggressive when shared vars are used
- My reachable processing was too aggressive, I'm putting this into conversion regression testing.
- 08:09 PM Bug #2061: unreachable code is too aggressive when shared vars are used
- I've checked converted sources, there is some resurrected dead-code in MAJIC that should not affect runtime; MAJIC di...
- 07:02 PM Bug #2061: unreachable code is too aggressive when shared vars are used
- renamed to not conflict...
- 07:00 PM Bug #2061: unreachable code is too aggressive when shared vars are used
- This code fixes this testcase, I will test the server file and regression conversion testing.
- 08:00 PM Bug #2060 (Closed): forward function definitions that include a parameter name can "fixup" missin...
- 08:00 PM Bug #2060: forward function definitions that include a parameter name can "fixup" missing paramet...
- Passed conversion and is checked into bzr as revision 10216.
02/26/2013
- 06:37 PM Bug #2061: unreachable code is too aggressive when shared vars are used
- I think the solution is to not remove vars/buffers/etc marked as unreachable if there are reachable nodes with a refi...
- 06:00 PM Bug #2061: unreachable code is too aggressive when shared vars are used
- unreachable code is removed and with it defined vars. following conversion fails:...
- 05:58 PM Bug #2061 (Closed): unreachable code is too aggressive when shared vars are used
- 05:01 PM Feature #1884: add some of the v10 data types and core built-ins
- Passed conversion regression testing, committed to bzr revision 10215.
- 03:25 PM Feature #1884: add some of the v10 data types and core built-ins
- The server project has a case of:...
- 04:15 PM Bug #2060: forward function definitions that include a parameter name can "fixup" missing paramet...
- Attached is the update that resolves this issue. It will duplicate the non-forward function definition's buffer para...
- 02:58 PM Bug #2060: forward function definitions that include a parameter name can "fixup" missing paramet...
- I tested various combinations of other parameter types:
- the regular AS "primitive" types (CHAR, INT, LOGICAL...)... - 12:55 PM Bug #2060: forward function definitions that include a parameter name can "fixup" missing paramet...
- In #1985 (see notes 29, 36 - 43 in that task) we found that forward function definitions that include a parameter nam...
- 12:52 PM Bug #2060 (Closed): forward function definitions that include a parameter name can "fixup" missin...
- 02:36 PM Bug #2056: null value for an annotation while persisting the AST
- The NPE is thrown because the function "copy_as_widget" attempts to duplicate an incomplete (missing "getter" annotat...
- 10:13 AM Bug #2056: null value for an annotation while persisting the AST
- Ovidiu, for now try and fix the "display c @ b as datatype" case, leave that for later.
- 10:12 AM Bug #2056: null value for an annotation while persisting the AST
- I looked into manuals about the @base-field specification, but they only describe how data is displayed into the resp...
- 08:25 AM Bug #2056: null value for an annotation while persisting the AST
- Note that the following case is converted correctly by P2J:...
- 08:17 AM Bug #2056: null value for an annotation while persisting the AST
- This is a task that tracks the issues reported by Eric in #1985, note 19.
I tried to eliminate the issue by pinpoint... - 08:05 AM Bug #2056 (Closed): null value for an annotation while persisting the AST
- 12:13 PM Feature #2050: ATTR_POLY/METH_POLY used as rvalue or in expressions
- Passed conversion testing and is checked in as bzr revision 10211. Runtime recursion testing is deferred.
- 10:57 AM Feature #2050: ATTR_POLY/METH_POLY used as rvalue or in expressions
- The issue is caused by the over-simplistic recursion protection in our context analysis. In addition, even in the ca...
- 10:53 AM Feature #2050: ATTR_POLY/METH_POLY used as rvalue or in expressions
- From #1985:
ra/ folder fails with:... - 03:42 AM Feature #2050: ATTR_POLY/METH_POLY used as rvalue or in expressions
- > Somehow, the improved expression typing changes the INPUT FUNC_POLY processing. As far as I know, these are equiva...
- 08:52 PM Feature #2050: ATTR_POLY/METH_POLY used as rvalue or in expressions
- I believe this is passing conversion testing.
The following diffs are present:... - 07:50 PM Feature #2050: ATTR_POLY/METH_POLY used as rvalue or in expressions
- Yes, it does seem to resolve the problem in raam/. Now we get a different error (see #1985).
- 07:48 PM Feature #2050: ATTR_POLY/METH_POLY used as rvalue or in expressions
- I have implemented major changes to ExpressionConversionWorker.expressionType() to do the following:
1. Add suppor... - 10:40 AM Feature #1920: implement persistent procedures
- Conversion regression testing has passed, committed to bzr revision 10210.
- 09:05 AM Feature #1920: implement persistent procedures
- It looks good.
- 08:58 AM Feature #1920: implement persistent procedures
- The removeQuotes change, I'm running regression conversion testing again.
- 08:55 AM Feature #1920: implement persistent procedures
- OK, so I'm dropping the functions.rules change and I'll change CommonAstSupport.removeQuotes. Note that removeQuotes ...
- 08:44 AM Feature #1920: implement persistent procedures
- OK. You can use the same approach as progressToJavaString() for dropping the quotes (and any following options):
<... - 08:41 AM Feature #1920: implement persistent procedures
- About issue 1: I don't think is OK to convert the string to Java, as currently I need to match with a Progress legacy...
- 08:35 AM Feature #1920: implement persistent procedures
- Code Feedback:
1. Strings can be qualified with more than just the @:U@. Your code assumes there can only be 1 qu... - 07:33 AM Feature #1920: implement persistent procedures
- No changes in generated MAJIC sources. Greg, if the update looks good to you, I will release it.
- 05:55 AM Feature #1920: implement persistent procedures
- Handle the case of single quotes used with function names and others (removeQuotes was improved to remove enclosing s...
- 05:44 AM Feature #1920: implement persistent procedures
- This update fixes a bug in dynamic-function's func name resolution, for cases like:...
- 08:21 AM Feature #2048 (Closed): BUFFER parameters without name in forward function definitions
- 06:17 AM Feature #2048: BUFFER parameters without name in forward function definitions
- Commited to bazaar as revision number 10209.
- 05:44 AM Feature #2048: BUFFER parameters without name in forward function definitions
- Update has passed conversion regression testing, please check in and distribute.
- 04:46 AM Feature #2048: BUFFER parameters without name in forward function definitions
- The update looks OK, is going through conversion regression testing now.
- 04:44 AM Feature #2048: BUFFER parameters without name in forward function definitions
- Added proposed update
- 07:58 PM Feature #2051 (Closed): conversion support for ATTR_POLY/METH_POLY used as rvalue or in expression
02/25/2013
- 02:36 PM Feature #1647: implement an option for SETUSERID and USERID to be backed by a replacement for the...
- Committed in bzr as 10203.
- 02:27 PM Feature #1647: implement an option for SETUSERID and USERID to be backed by a replacement for the...
- Conversion testing passed. Please check this in and distribute it.
- 12:49 PM Feature #1647: implement an option for SETUSERID and USERID to be backed by a replacement for the...
- This looks good. I will put it into conversion testing now.
- 12:41 PM Feature #1647: implement an option for SETUSERID and USERID to be backed by a replacement for the...
- The suggested update has been uploaded. Also I have appended simple test and conversion result. The code drop merged ...
- 09:49 AM Feature #1647: implement an option for SETUSERID and USERID to be backed by a replacement for the...
- I should have provided more information previously, sorry.
For now, all that needs to be done is to add support fo... - 09:42 AM Feature #1647: implement an option for SETUSERID and USERID to be backed by a replacement for the...
- Let me clarify some points.
1. Is the _USER table already implemented in P2J?
2. My work is to add conversion suppo... - 02:27 PM Bug #2049 (Closed): SET statement and NO-ERROR clause
- 02:25 PM Bug #2049: SET statement and NO-ERROR clause
- Conversion testing has passed. I have checked it in as bzr revision 10102.
- 12:11 PM Bug #2049: SET statement and NO-ERROR clause
- But since I haven't tested that assumption (that no-error always will appear at the end), I think it is best to go wi...
- 12:09 PM Bug #2049: SET statement and NO-ERROR clause
- Added the new archive, I will remove the older, unneeded one.
I believe that @isWidget@ is used as a flag when sca... - 11:37 AM Bug #2049: SET statement and NO-ERROR clause
- It is not clear to me whether we should have a section like this:...
- 11:15 AM Bug #2049 (Review): SET statement and NO-ERROR clause
- Looks like the @N0-ERROR@ clause was treated as an widget in the list of parameters of the statements (@SET@, @ASSIGN...
- 11:04 AM Bug #2049 (WIP): SET statement and NO-ERROR clause
- 08:58 AM Bug #2049: SET statement and NO-ERROR clause
- Conversion fails in a case like...
- 08:57 AM Bug #2049 (Closed): SET statement and NO-ERROR clause
- 02:20 PM Feature #2048: BUFFER parameters without name in forward function definitions
- Keep in mind that the FORWARD declaration should not be changing buffer scoping at all. My guess is that somewhere w...
- 02:19 PM Feature #2048: BUFFER parameters without name in forward function definitions
- Actually, both results look wrong. doubler2() gets an openScope() with the same buffer name passed twice. That may ...
- 01:59 PM Feature #2048: BUFFER parameters without name in forward function definitions
- The conversion fails because of code in record_scoping_prep.rules which assumes the buffer annotation is in the copy....
- 08:56 AM Feature #2048: BUFFER parameters without name in forward function definitions
- Conversion fails in this case:...
- 08:53 AM Feature #2048 (Closed): BUFFER parameters without name in forward function definitions
- 11:21 AM Feature #2050: ATTR_POLY/METH_POLY used as rvalue or in expressions
- The issue only occurs for those ATTR_POLY/FUNC_POLY/METH_POLY cases where we cannot detect the type based on the chil...
- 10:20 AM Feature #2050: ATTR_POLY/METH_POLY used as rvalue or in expressions
- I wonder if ExpressionConversionWorker should ignore these _POLY cases ? And determine the expression type based on t...
- 10:16 AM Feature #2050: ATTR_POLY/METH_POLY used as rvalue or in expressions
- The problem I was working (in #1655) is the same problem. I "fixed" it by eliminating the use of expressionType() in...
- 10:02 AM Feature #2050: ATTR_POLY/METH_POLY used as rvalue or in expressions
- Conversion for ATTR_POLY used in complex expressions fails, as the ExpressionConversionWorker can't determine the typ...
- 09:56 AM Feature #2050 (Closed): ATTR_POLY/METH_POLY used as rvalue or in expressions
- 09:57 AM Feature #2051: conversion support for ATTR_POLY/METH_POLY used as rvalue or in expression
- This is for milestone 4 time tracking only. All comments must be added in parent task #2050
- 09:57 AM Feature #2051 (Closed): conversion support for ATTR_POLY/METH_POLY used as rvalue or in expression
02/24/2013
- 03:52 PM Feature #1627 (Closed): support for empty EXPORT statements
- 03:43 PM Feature #1627: support for empty EXPORT statements
- The evl_upd20130224a.zip has been committed in bzr as 10197.
- 03:32 PM Feature #1627: support for empty EXPORT statements
- This has passed conversion testing. Go ahead and check it in and distribute it.
- 02:33 PM Feature #1627: support for empty EXPORT statements
- The code looks good. I will run conversion testing now.
- 01:43 PM Feature #1627: support for empty EXPORT statements
- The modified post_parse_fixups.xml and new rule have been uploaded to eliminate empty export. Also the converted code...
- 06:16 AM Feature #2013: implement the SELF system handle
- Committed to bzr revision 10194, passed runtime regression testing.
02/23/2013
- 05:43 PM Feature #2013: implement the SELF system handle
- The change looks fine. This is being conversion tested now.
- 01:30 PM Feature #2013: implement the SELF system handle
- Fixed initialization of context-local data in SelfManager.
- 10:14 PM Feature #2013: implement the SELF system handle
- Passed conversion testing. Checked into bzr as 10189.
- 05:27 PM Feature #2021 (Closed): conversion support for web services
- 05:26 PM Feature #1645: implement web services support
- With this change, testing passed. Checked into bzr as 10193.
- 04:19 PM Feature #1645: implement web services support
- This update causes a problem with many (all?) RUN statements. Here is a common example diff (this is broken througho...
- 12:21 PM Feature #1645: implement web services support
- This is in testing now.
- 11:54 AM Feature #1645: implement web services support
- It looks good. This will go into conversion testing next.
- 11:46 AM Feature #1645: implement web services support
- Attached update fixes the refAsync issue and refSet.move (which should move to copy not refAsync)
- 11:39 AM Feature #1645: implement web services support
- Everything else looks OK with the code.
- 11:38 AM Feature #1645: implement web services support
- In fixups/control_flow.rules refAsync is never assigned, but it is relied upon in the ASYNCH ON case and in the SET h...
- 11:26 AM Feature #1645: implement web services support
- Built on top of #1782 23d.zip update. Fixed support for @RUN ... SET hPortType ON hWebServ@ statement. Added support ...
- 08:39 AM Feature #1645: implement web services support
- More info about RUN ... SET ... ON SERVER. Something like this works:...
- 05:28 AM Feature #1645: implement web services support
- Another later edit: it is possible to use the @SET hPortType@ specification even with the @TRANSACTION DISTINCT@ and ...
- 04:51 AM Feature #1645: implement web services support
- > fix the @RUN SET ... ON SERVER@ statement
Look like the ASYNC clause is supported (at least at compile-time) for th... - 04:28 AM Feature #1645: implement web services support
- For the Server object handle, all documented attributes/methods are supported except these:
# REQUEST-INFO, RESPONSE... - 11:51 AM Feature #2041 (Closed): implement runtime support for "shared" attributes that are just stubbed
- 11:50 AM Feature #2002 (Closed): refactor some "shared" attributes
- 10:14 PM Feature #2014 (Closed): conversion support for SELF system handle
02/22/2013
- 04:31 PM Feature #2013: implement the SELF system handle
- Here is the right version.
- 04:27 PM Feature #2013: implement the SELF system handle
- This is the latest version merged up to bzr 10188. It will go into testing next.
- 02:17 PM Feature #2013: implement the SELF system handle
- > I think it might be more correct to say that the rule-set only handles the resource reference for handle types. In...
- 01:46 PM Feature #2013: implement the SELF system handle
- The code looks good....
- 01:33 PM Feature #2013: implement the SELF system handle
- > 1. refName is a dead variable and can be removed from methods_attributes.rules.
OK, removed
> 2. How do we emit t... - 12:34 PM Feature #2013: implement the SELF system handle
- Code Feedback:
1. refName is a dead variable and can be removed from methods_attributes.rules.
2. How do we emi... - 12:14 PM Feature #2013: implement the SELF system handle
- Conversion regression testing has passed - compilation was OK, all changes are expected.
- 06:39 AM Feature #2013: implement the SELF system handle
- Conversion has finished, there was a APPLY ... TO SELF problem, fixed in attached update. All other changes look good...
- 03:22 AM Feature #2013: implement the SELF system handle
- Added testcases (previous were for session handle)
- 03:20 AM Feature #2013: implement the SELF system handle
- -Added testcases.- they are for session handle, I've deleted it from here.
- 03:18 AM Feature #2013: implement the SELF system handle
- Fixed a conversion error, I'm running conversion again.
- 01:21 PM Feature #2003 (Closed): conversion support for SESSION handle
- 01:16 PM Feature #1612: finish SESSION system handle support
- Committed to bzr revision 10187.
- 01:03 PM Feature #1612: finish SESSION system handle support
- Conversion testing has passed. Please check in and distribute.
- 12:02 PM Feature #1612: finish SESSION system handle support
- The update looks good. I'm testing it now.
- 11:43 AM Feature #1612: finish SESSION system handle support
- Merged with revision 10186.
- 11:10 AM Feature #1612: finish SESSION system handle support
- The code looks fine. I'll re-check after the merge.
- 03:22 AM Feature #1612: finish SESSION system handle support
- Added tests.
- 03:19 AM Feature #1612: finish SESSION system handle support
- Merged with 10183, fixed some runtime errors too (ERROR-STATUS handle could not initialize its static proxy).
- 11:53 AM Feature #2009 (Closed): conversion support for LANDSCAPE/PORTRAIT I/O option
- 11:49 AM Feature #2011 (Closed): conversion support for _MSG() built-in
- 11:46 AM Feature #1632: implement _MSG() undocumented built-in function
- Conversion tests passed , commited to bazaar as revision 10186
- 09:03 AM Feature #1632: implement _MSG() undocumented built-in function
- The update looks good. I will start testing it shortly.
- 11:27 AM Feature #1631: implement support for LANDSCAPE/PORTRAIT in I/O statements
- Conversion test passed, commited to bazaar as revision 10185
- 09:10 AM Feature #1631: implement support for LANDSCAPE/PORTRAIT in I/O statements
- The update looks good. I will start testing it shortly. I am deleting the update that is not matching, so that ther...
- 09:07 AM Feature #1631: implement support for LANDSCAPE/PORTRAIT in I/O statements
- Attached it
- 09:06 AM Feature #1631: implement support for LANDSCAPE/PORTRAIT in I/O statements
- This is the wrong update (it is for the _MSG work). Please post the correct one.
- 04:26 AM Feature #1631: implement support for LANDSCAPE/PORTRAIT in I/O statements
- Added merged update
- 11:14 AM Feature #1979 (Closed): conversion support for DOM XML processing
- 11:10 AM Feature #1640: implement DOM XML support
- The update evl_upd20130222a.zip passed the conversion test and committed in bzr as 10184.
- 09:02 AM Feature #1640: implement DOM XML support
- The update looks good. I will start testing it shortly.
- 05:56 AM Feature #1640: implement DOM XML support
- The merged code has been uploaded for testing. The setSubType methods unified with name syntax of the SubTypeAttribut...
- 03:02 AM Feature #2002: refactor some "shared" attributes
- Committed to bzr revision 10182.
02/21/2013
- 02:55 PM Feature #2002: refactor some "shared" attributes
- FYI:...
- 01:33 PM Feature #2002: refactor some "shared" attributes
- Fixed issues 1 to 4, merged with 10181.
- 01:24 PM Feature #2002: refactor some "shared" attributes
- Greg Shah wrote:
> 6. Wasn't the idea behind the BufferField design was to avoid get/set methods that could conflict... - 01:13 PM Feature #2002: refactor some "shared" attributes
- > 1. Please put a TODO comment into BrowseColumnWidget that it should not always return "FILL-IN" as its type. From ...
- 12:50 PM Feature #2002: refactor some "shared" attributes
- Code Review Feedback:
1. Please put a TODO comment into BrowseColumnWidget that it should not always return "FILL-... - 12:11 PM Feature #2002: refactor some "shared" attributes
- > Also, please prepare any Majic changes that need to be made.
See #2023 - 12:07 PM Feature #2002: refactor some "shared" attributes
- There are 2 check-ins that will occur shortly. Be prepared to merge up to the lastest level. Also, please prepare a...
- 10:45 AM Feature #2002: refactor some "shared" attributes
- There is one MAJIC-side change needed, as GenericWidget.getFormat now returns character instead of String (I chose to...
- 10:40 AM Feature #2002: refactor some "shared" attributes
- The only change in generated code is the one related to label: now it unwraps using @handle.unwrapCommonField@, inste...
- 05:40 AM Feature #2002 (WIP): refactor some "shared" attributes
- 05:33 AM Feature #2002: refactor some "shared" attributes
- This update cleans #1668 errors + refactors attributes. I'm running conversion now, I'll let you know how it goes.
L... - 12:12 PM Feature #1640: implement DOM XML support
- I have looked into current bzr. There is one point need to be discussed. The attribute SUBTYPE has implemented as sta...
- 12:10 PM Feature #2013: implement the SELF system handle
- I'm leaving a conversion to run over night, hopefully all SELF-handle usage will convert nicely.
- 10:20 AM Feature #2013: implement the SELF system handle
- I like it.
- 06:23 AM Feature #2013 (WIP): implement the SELF system handle
- Attached update with proposed solution (built on top of revision 10179). With this approach, all attribute/method acc...
- 05:58 AM Feature #2013: implement the SELF system handle
- How I see this working: we have a SelfManager class which manages a stack of "self" handles. Each event responsible ...
- 11:47 AM Feature #1612: finish SESSION system handle support
- Added support for the high-priority stuff (built on top of revision 10179, was easier that way) plus stubs for some a...
- 07:12 AM Feature #1612: finish SESSION system handle support
- List of not supported attributes:
* progress.g parser errors:... - 08:00 AM Feature #1632: implement _MSG() undocumented built-in function
- Looks good. I will let you know when we can test. Only conversion regression testing will be needed. Be prepared t...
- 04:45 AM Feature #1632: implement _MSG() undocumented built-in function
- Corrected javadoc, was meant to say first: greater or equal 1, then I though greater than 0 to be better as descripti...
- 06:35 AM Feature #2003 (WIP): conversion support for SESSION handle
- 06:34 AM Feature #2014 (WIP): conversion support for SELF system handle
- 07:20 PM Feature #2022: runtime support for web services
- This task is only for time tracking and association with the milestone. All history goes in parent task #1645.
- 07:20 PM Feature #2022 (Closed): runtime support for web services
- 07:20 PM Feature #2021: conversion support for web services
- This task is only for time tracking and association with the milestone. All history goes in parent task #1645.
- 07:19 PM Feature #2021 (Closed): conversion support for web services
02/20/2013
- 06:57 PM Feature #1781: add missing support for the WIDGET-HANDLE builtin function
- After a quick review of the handle.java class and the builtin_functions.rules, I can see the following:
1. WIDGET-... - 06:20 PM Feature #1781: add missing support for the WIDGET-HANDLE builtin function
- The use cases (and even the description of the function) seem to be identical to the HANDLE() builtin function. A te...
- 02:09 PM Feature #1990 (Closed): conversion support for appserver
- 02:00 PM Feature #1608: implement full appserver support (from 4GL clients only)
- Committed to bzr revision 10179.
- 01:44 PM Feature #1608: implement full appserver support (from 4GL clients only)
- The changes passed regression testing. Please check them into bzr and distribute the update.
- 01:43 PM Feature #1632: implement _MSG() undocumented built-in function
- The code looks good. I only have 1 question. The javadoc says this:...
- 10:26 AM Feature #1632: implement _MSG() undocumented built-in function
- Added proposed update
- 10:07 AM Feature #1632: implement _MSG() undocumented built-in function
- OK, this is more clear.
As far as the negative numbers are concerned, we won't duplicate that behavior right now. ... - 09:26 AM Feature #1632: implement _MSG() undocumented built-in function
- I realized the 0 index difference happened because I mistakenly rerun the program in some cases using the character e...
- 09:03 AM Feature #1632: implement _MSG() undocumented built-in function
- Please upload the msg_test.txt and msg_test2.txt output files so that I can better understand what is going on.
> ... - 08:37 AM Feature #1632: implement _MSG() undocumented built-in function
- Done more testing and got a better understanding of how msg working.
It seems the _msg(int) will return the error num... - 12:02 PM Feature #2011 (Review): conversion support for _MSG() built-in
- 08:28 AM Feature #1631: implement support for LANDSCAPE/PORTRAIT in I/O statements
- It is good to go. I will let you know when we can schedule it. Because there are some updates in front, please be r...
- 03:04 AM Feature #1631: implement support for LANDSCAPE/PORTRAIT in I/O statements
- Added proposed update.
02/19/2013
- 05:21 PM Feature #2015: runtime support for SELF system handle
- This is just for time tracking and association with milestone 4. All history goes in parent task #2013.
- 05:21 PM Feature #2015 (Closed): runtime support for SELF system handle
- 05:21 PM Feature #2014: conversion support for SELF system handle
- This is just for time tracking and association with milestone 4. All history goes in parent task #2013.
- 05:20 PM Feature #2014 (Closed): conversion support for SELF system handle
- 05:19 PM Feature #2013: implement the SELF system handle
- The SELF system handle returns the handle to the resource currently being processed in a trigger or other callback pr...
- 05:15 PM Feature #2013 (Closed): implement the SELF system handle
- 05:03 PM Feature #1640: implement DOM XML support
- The update looks good. We will try to get it scheduled soon, but you will probably have to merge up to the bzr head ...
- 09:02 PM Feature #1640: implement DOM XML support
- The update for new attributes/methods has been uploaded for review.
- 04:57 PM Feature #1608: implement full appserver support (from 4GL clients only)
- We don't need to handle the Asynchronous request handle object for milestone 4. We will probably go ahead and implem...
- 08:59 AM Feature #1608: implement full appserver support (from 4GL clients only)
- This code fixes the unsuscribe_stmt clause (I've tested will all proc-related events tests and they passed). Conversi...
- 06:21 AM Feature #1608: implement full appserver support (from 4GL clients only)
- I don't see the Asynchronous request object handle mentioned in this task, but please let me know if this is necessar...
- 04:33 PM Feature #2002: refactor some "shared" attributes
- Please go ahead with this task in combination with #1974 (#1668). Prepare a single update that cleans all of this up.
- 01:32 PM Feature #2002: refactor some "shared" attributes
- I think the best grouping should be this:
# COLUMN-LABEL (BUFFER-FIELD), DATA-TYPE(BUFFER-FIELD, WIDGET), FORMAT(BUF... - 08:51 AM Feature #2002: refactor some "shared" attributes
- Except DATA-TYPE and FORMAT (which are common for BUFFER-FIELD and widgets), I don't see any way of grouping these at...
- 03:34 PM Feature #1631: implement support for LANDSCAPE/PORTRAIT in I/O statements
- Feedback:
Please fix the code formatting issues in Stream.java (there are several):
1. Header # is wrong.
2. W... - 12:08 PM Feature #1631: implement support for LANDSCAPE/PORTRAIT in I/O statements
- Added proposed update
- 07:07 PM Feature #1631: implement support for LANDSCAPE/PORTRAIT in I/O statements
- The following is an example of the option in use:...
- 02:20 PM Feature #1632: implement _MSG() undocumented built-in function
- From your status report:
> Tested the _msg function , results seems to not be consistent for the same value.
P... - 07:12 PM Feature #1632: implement _MSG() undocumented built-in function
- This is an undocumented built-in function. We need to determine what it does. at a high level it is used to create ...
- 12:09 PM Feature #2011 (WIP): conversion support for _MSG() built-in
- 07:13 PM Feature #2011: conversion support for _MSG() built-in
- This task is only for time tracking and association with milestone 4. All history should be placed in the parent tas...
- 07:13 PM Feature #2011 (Closed): conversion support for _MSG() built-in
- 05:03 AM Feature #2009 (WIP): conversion support for LANDSCAPE/PORTRAIT I/O option
- 07:01 PM Feature #2009: conversion support for LANDSCAPE/PORTRAIT I/O option
- This task is only for time tracking and association with milestone 4. All history should be placed in the parent tas...
- 07:01 PM Feature #2009 (Closed): conversion support for LANDSCAPE/PORTRAIT I/O option
- 07:14 PM Feature #2012: runtime support for _MSG() built-in
- This task is only for time tracking and association with milestone 4. All history should be placed in the parent tas...
- 07:14 PM Feature #2012 (Closed): runtime support for _MSG() built-in
- 07:02 PM Feature #2010: runtime support for LANDSCAPE/PORTRAIT I/O options
- This task is only for time tracking and association with milestone 4. All history should be placed in the parent tas...
- 07:02 PM Feature #2010 (Closed): runtime support for LANDSCAPE/PORTRAIT I/O options
02/18/2013
- 06:39 PM Feature #1627: support for empty EXPORT statements
- Good. Then the solution is to do the following:
1. In post_parse_fixups.rules, you should add a new rule-set like... - 05:35 PM Feature #1627: support for empty EXPORT statements
- > Let me make sure I understand. In export_test[1-3].p, if you remove the empty EXPORT statement from those files, do...
- 05:20 PM Feature #1627: support for empty EXPORT statements
- > This redirects output to the file and produces non-empty file with real values of the variable like printing to the...
- 04:29 PM Feature #1627: support for empty EXPORT statements
- > When a stream is not explicitly used (e.g. EXPORT STREAM my-stream...) then you must first redirect the terminal li...
- 04:15 PM Feature #1627: support for empty EXPORT statements
- > EXPORT cannot be used with output to the screen. (1105)
When a stream is not explicitly used (e.g. EXPORT STREAM... - 02:55 PM Feature #1627: support for empty EXPORT statements
- The statements
EXPORT var1 (some-var2 + 54) var3.
EXPORT database-table.
both have run-time error in 4GL:
...
E... - 09:59 AM Feature #1627: support for empty EXPORT statements
- It is possible to have an "empty" EXPORT statement in the 4GL, as in:...
- 06:19 PM Feature #1979 (WIP): conversion support for DOM XML processing
- 06:19 PM Feature #1640: implement DOM XML support
- I have found that the following are actually in use in the application and need to be added for milestone 4:
Attri... - 05:46 PM Feature #2004: runtime support for SESSION handle
- This task is just for time tracking and association with milestone 4. Put all history into the parent task #1612.
- 05:46 PM Feature #2004 (Closed): runtime support for SESSION handle
- 05:45 PM Feature #2003: conversion support for SESSION handle
- This task is just for time tracking and association with milestone 4. Put all history into the parent task #1612.
- 05:45 PM Feature #2003 (Closed): conversion support for SESSION handle
- 05:43 PM Feature #1612: finish SESSION system handle support
- The following are high priority:
Attributes:
CLIENT-TYPE
FIRST-BUFFER
NUMERIC-SEPARATOR
NUMERIC-DECIMAL-POIN... - 05:14 PM Feature #1608: implement full appserver support (from 4GL clients only)
- I have reviewed the code, the only problem is that the unsubscribe_stmt still cannot match on the event name after th...
- 04:25 PM Feature #1608: implement full appserver support (from 4GL clients only)
- Attached update with the mentioned issues fixed.
- 04:19 PM Feature #1608: implement full appserver support (from 4GL clients only)
- > OK, so the idea the front phase should leave the ASTs as unchaged as possible.
Yes, that's right.
> Please le... - 04:10 PM Feature #1608: implement full appserver support (from 4GL clients only)
- > I'm in the middle of the code review, but there is at least 1 major issue. The subscribe_stmt and unsubscribe_stmt...
- 03:46 PM Feature #1608: implement full appserver support (from 4GL clients only)
- More Feedback:
1. handle.java is missing the "--JPRM--" in the header.
2. Is HandleChain.setType() always going... - 03:25 PM Feature #1608: implement full appserver support (from 4GL clients only)
- Code Review Feedback:
I'm in the middle of the code review, but there is at least 1 major issue. The subscribe_st... - 02:32 PM Feature #1608: implement full appserver support (from 4GL clients only)
- Merged with revision 10178.
- 02:01 PM Feature #1608: implement full appserver support (from 4GL clients only)
- Attached update provides conversion support for app-server related statements and attributes/methods. Fixes progress....
- 12:00 PM Feature #1608: implement full appserver support (from 4GL clients only)
- Greg Shah wrote:
> You will have to remove the expr option from that rule.
Yes, expr from widget_qualifier is no lo... - 10:44 AM Feature #1608: implement full appserver support (from 4GL clients only)
- I don't have a problem with your approach. I think it may work, but I do suspect there will be lookahead issues. Yo...
- 08:28 AM Feature #1608: implement full appserver support (from 4GL clients only)
- I think the final solution is to get rid of the allowInProc quirk and call the widget_qualifier rule (in lvalue) only...
- 04:20 PM Feature #1994 (Closed): conversion support for SOAP
- 03:13 PM Feature #2002: refactor some "shared" attributes
- Please implement appropriate interfaces for the following attributes which are shared between multiple resources:
... - 03:04 PM Feature #2002 (Closed): refactor some "shared" attributes
- 02:25 PM Feature #1644: implement SOAP support
- No changes in generated MAJIC sources, committed to bzr revision 10178.
- 09:37 AM Feature #1644: implement SOAP support
- And the latest update...
- 09:37 AM Feature #1644: implement SOAP support
- I've removed the trailing quotes. The conversion has been started on staging (with previous generated sources backedup).
- 09:24 AM Feature #1644: implement SOAP support
- I am OK with the update. The only thing I suggest is that the new javadoc entries have an unmatched trailing double ...
- 09:14 AM Feature #1644: implement SOAP support
- Added update merged with bzr revision 10177.
- 07:58 AM Feature #1644: implement SOAP support
- > For these, 4GL allows only integer and int64 values (confirmed by testing).
OK. Please use long instead of int ... - 03:37 AM Feature #1644: implement SOAP support
- > 1. The ErrorManager.WorkArea.soapFault member needs javadoc.
OK
> 2. For int parameters to methods like getHeader... - 09:26 AM Feature #1987 (Closed): conversion support for SAX
- 09:21 AM Feature #1620: implement EXTENT parameter support
- Added testcases, for reference (they are in bzr too).
- 08:29 AM Feature #1620: implement EXTENT parameter support
- ca_upd20130218a.zip has been committed as 10175 (has passed regression testing).
- 03:59 AM Feature #1620: implement EXTENT parameter support
- This update fixes the following issues discovered on Saturday, during regression testing:
* ControlFlowOps NPE
* Bl... - 09:18 AM Feature #1641: implement SAX XML support
- The following attributes(SAX XML support) not yet implemented according to your note(a means SaxAttr, r means SaxRead...
- 09:05 AM Feature #1641: implement SAX XML support
- I have not cross-referenced your final code with the list of all possible features. Can you please make a list of al...
- 08:28 AM Feature #1641: implement SAX XML support
- evl_upd20130215b.zip has been committed as 10176.
02/17/2013
- 12:05 PM Feature #1644: implement SOAP support
- Code Review Feedback:
1. The ErrorManager.WorkArea.soapFault member needs javadoc.
2. For int parameters to met... - 11:25 AM Feature #1644: implement SOAP support
- OK, I understand now. Yes, this is an unfortunate side effect of our implementation. But at least the duplicate imp...
- 11:17 AM Feature #1608: implement full appserver support (from 4GL clients only)
- > Do you want us to get into the high-level design of the appserver's dispatcher/thread pool, startup/shutdown/connec...
02/16/2013
- 05:15 PM Feature #1608: implement full appserver support (from 4GL clients only)
- Greg: as a side-note, at this time, how much of the runtime do you want to be stubbed out ? Do you want us to get int...
- 11:53 AM Feature #1608: implement full appserver support (from 4GL clients only)
- > do we have handle fields in the project?
Yes. I think they may only be supported in temp-tables in the 4GL. We... - 10:04 AM Feature #1608: implement full appserver support (from 4GL clients only)
- > 1. Determine the limits of what can be matched from the following "IN handle" cases:
For all cases, the @handle@ ca... - 09:19 AM Feature #1608: implement full appserver support (from 4GL clients only)
- > (thus the current approach of converting TRANSACTION DISTINCT to a KW_TRANS_DS token will not be correct).
You c... - 09:04 AM Feature #1608: implement full appserver support (from 4GL clients only)
- > I assume that you don't need to change the looping of the parser. Instead you are referring to using fixups to for...
- 08:32 AM Feature #1608: implement full appserver support (from 4GL clients only)
- Some thoughts:
> The RUN statement's clauses can be "switched" to some extent and produce valid code in 4GL, and t... - 07:35 AM Feature #1608: implement full appserver support (from 4GL clients only)
- And another PS: the SET clause for the ASYNCHRONOUS case behaves interesting:
* SET clause can be used without the A... - 07:24 AM Feature #1608: implement full appserver support (from 4GL clients only)
- PS: there is one syntax which can't be fixed that easy. Is related to RUN ... IN, as:...
- 07:20 AM Feature #1608: implement full appserver support (from 4GL clients only)
- The RUN statement's clauses can be "switched" to some extent and produce valid code in 4GL, and the conclusion is the...
- 12:40 PM Feature #1644: implement SOAP support
- > In each case where we are doing something different that the 4GL documentation, please make a statement like this:
... - 12:26 PM Feature #1644: implement SOAP support
- I will review it later today. Be prepared to merge it Monday morning with the pending 10174-10176 that is currently ...
- 12:07 PM Feature #1644: implement SOAP support
- Attached update adds conversion support for SOAP-related attributes/methods and statements. Everything is stubbed, un...
- 09:08 AM Feature #1644: implement SOAP support
- I like the plan.
In regard to the "common" attributes (UNIQUE-ID, INSTANTIATING-PROCEDURE, LOCALNAME, NAMESPACE-UR... - 02:42 AM Feature #1620: implement EXTENT parameter support
- This update:
- fixes decimals clause for 1-extent fields.
- fixes javadoc
- adds a TODO in decimal.setPrecision, f... - 07:44 PM Feature #1620: implement EXTENT parameter support
- FYI, there are some javadoc errors. You can fix them later (in a different check in)....
- 07:07 PM Feature #1641: implement SAX XML support
- This is merged on top of ca_upd20130215d.zip (#1608) and ca_upd20130215e.zip (#1620 and #1621). It MUST be applied A...
02/15/2013
- 05:47 PM Feature #1641: implement SAX XML support
- It looks good. I will merge it on top of Constantin's update and upload the result here.
- 05:21 PM Feature #1641: implement SAX XML support
- The update merged with bzr 10173 has been uploaded.
- 02:06 PM Feature #1641: implement SAX XML support
- I appreciate it, but there are 3 of us that need to merge and it will be easier to use bzr.
- 02:00 PM Feature #1641: implement SAX XML support
- > Normally, we only check in after everything is passed in regression testing. For today only, I have asked Eric to c...
- 01:46 PM Feature #1641: implement SAX XML support
- Normally, we only check in after everything is passed in regression testing. For today only, I have asked Eric to ch...
- 01:21 PM Feature #1641: implement SAX XML support
- > ...
> 2. Merge with the bzr check-ins that should happen from the updates being tested in staging.
> ...
Does ... - 12:35 PM Feature #1641: implement SAX XML support
- Code Review Feedback:
1. Change the Abstract and class Javadoc in XmlFactory and XEntity so that they mention both... - 08:05 PM Feature #1641: implement SAX XML support
- The SAX conversion and test file has been uploaded for you to review. Merged with recent P2J codebase.
The UniqueI... - 03:22 PM Feature #1620: implement EXTENT parameter support
- Attached update merged with bzr revision 10173.
- 12:09 PM Feature #1620: implement EXTENT parameter support
- Unfortunately the conversion on the linux box crashed when it was almost at the end, so I will not have a conclusion ...
- 11:32 AM Feature #1620: implement EXTENT parameter support
- OK, I've checked again and looks like I've been miss-interpreting the diff result, this update actually solves the is...
- 11:26 AM Feature #1620: implement EXTENT parameter support
- Do these problems already exist in Majic today?
- 11:20 AM Feature #1620: implement EXTENT parameter support
- What I'm currently reconverting doesn't fix the dead-vars emitted in validateExpression and validateMessage methods. ...
- 11:12 AM Feature #1620: implement EXTENT parameter support
- The code looks good. Assuming your tests show that it needs no further changes, the plan is as follows:
1. As soo... - 07:02 AM Feature #1620: implement EXTENT parameter support
- After checking the converted sources, the following issues were fixed/found:
# in some programs, the validation expr... - 12:52 PM Feature #1608: implement full appserver support (from 4GL clients only)
- The delete widget changes look good. We will keep it separate from the rest of the appserver update and instead incl...
- 12:19 PM Feature #1608: implement full appserver support (from 4GL clients only)
- PS: I suggest to test and release this together with the #1620 changes, as we will be able to integrate the Deletable...
- 12:12 PM Feature #1608: implement full appserver support (from 4GL clients only)
- This update adds the Deletable interface and DELETE WIDGET support (note that with DELETE WIDGET any kind of resource...
- 09:37 AM Feature #1608: implement full appserver support (from 4GL clients only)
- Interesting finding. The permutations never seem to end. This also has implications about our runtime implementatio...
- 09:17 AM Feature #1608: implement full appserver support (from 4GL clients only)
- OK, I will work on this. I will not push this change to all resources yet, only to what we are currently working.
... - 09:11 AM Feature #1608: implement full appserver support (from 4GL clients only)
- Good idea. Please go with the Deletable approach.
Also: please add support for DELETE WIDGET, which is the equiva... - 08:55 AM Feature #1608: implement full appserver support (from 4GL clients only)
- A note about delete: currently, each deletable resource must be registered in HandleOps.delete and call its dedicated...
- 11:17 AM Feature #1994 (WIP): conversion support for SOAP
- 11:02 AM Feature #1644: implement SOAP support
- Implementation details:
* SOAPFactory - class with APIs for CREATE SOAP-HEADER and CREATE SOAP-HEADER-ENTRYREF state...
02/14/2013
- 06:15 PM Feature #1641: implement SAX XML support
- > How soon can you provide an update for these features?
In a hour or so. I need to sync with the latest code, mak... - 06:02 PM Feature #1641: implement SAX XML support
- How soon can you provide an update for these features?
- 02:15 PM Feature #1608: implement full appserver support (from 4GL clients only)
- Some quick notes on the update:
* SSL-SERVER-NAME (converted to SslServerAttribute interface) - make sure you don't ... - 02:00 PM Feature #1608: implement full appserver support (from 4GL clients only)
- Added an intermediate update for refference, the update does not contain implementation for the following server attr...
- 08:32 AM Feature #1608: implement full appserver support (from 4GL clients only)
- Good idea.
- 08:31 AM Feature #1608: implement full appserver support (from 4GL clients only)
- A note about emitting null for missing clauses: we can't map null with a 4GL token, so instead the solution is to cre...
- 02:02 PM Feature #1990 (WIP): conversion support for appserver
- 01:25 PM Feature #1620: implement EXTENT parameter support
- > 1. I assume you have resolved the TRPL expression parsing error? If not, then we must solve this before going into...
- 01:06 PM Feature #1620: implement EXTENT parameter support
- Code Review Feedback:
This version looks good. I am fine with this, however I have questions:
1. I assume you ... - 11:25 AM Feature #1620: implement EXTENT parameter support
- Attached version does the following:
# there is a feature which I think is valid only in 4GL v9:... - 08:31 AM Feature #1620: implement EXTENT parameter support
- ...
- 12:12 AM Feature #1620: implement EXTENT parameter support
- About issue 3 - I chose 0 to represent dynamic extent because this will produce a valid reference in the converted co...
- 07:02 PM Feature #1620: implement EXTENT parameter support
- Feedback:
1. The int members of enum ArgValidationErrors in ControlFlowOps need javadoc.
2. The progress.g need... - 12:29 PM Feature #1956 (Closed): implement conversion support for sockets
- 12:10 PM Feature #1644: implement SOAP support
- ...
- 08:51 AM Feature #1639: implement socket support
- Committed conversion support for socket to bazaar as rev. 10167 and sent update mail to the team.
- 07:08 PM Feature #1995: runtime support for SOAP
- This is just for time tracking. All history should be in parent task #1644.
- 07:07 PM Feature #1995 (Closed): runtime support for SOAP
- 07:07 PM Feature #1994: conversion support for SOAP
- This is just for time tracking and association with milestone 4. All history should be in the parent task #1644.
- 07:07 PM Feature #1994 (Closed): conversion support for SOAP
02/13/2013
- 03:03 PM Feature #1620 (Review): implement EXTENT parameter support
- 11:14 AM Feature #1620: implement EXTENT parameter support
- Beside the issues on comment 28, the attached fix adds only some startup code for extent parameter validation. What i...
- 09:18 AM Feature #1620: implement EXTENT parameter support
- > 1. def_var_stmt
No special work needed, define_stmt calls sym.annotateVariableOptions which sets the extent annota... - 12:39 PM Feature #1641: implement SAX XML support
- Both of these are only used for SAX and DOM, so they can go in an XCommon interface.
- 12:30 PM Feature #1641: implement SAX XML support
- The other common attributes/methods:
NONAMESPACE-SCHEMA-LOCATION attribute(common with X-Document object)
ADD-SCHEMA... - 12:09 PM Feature #1641: implement SAX XML support
- Actually, UNIQUE-ID is common to more than just the DOM and SAX support. Other resources (e.g. procedure handles, SO...
- 08:45 AM Feature #1641: implement SAX XML support
- I have encountered one issue. The attribute
UNIQUE-ID
is common not only for SAX XML objects but for DOM XML too. S...
02/12/2013
- 02:57 PM Feature #1620: implement EXTENT parameter support
- I'm implementing these rules from last to first, and not obvious cases I'll leave last. About the validation problems...
- 12:52 PM Feature #1620: implement EXTENT parameter support
- Wow. Great work!
If we are far off from this implementation, then we will need to defer the runtime work until lat... - 11:40 AM Feature #1620: implement EXTENT parameter support
- List of rules describing behavior of mixed extent and dynamic-extent in parameters and assignments:
1. output mode:
... - 09:43 AM Feature #1620: implement EXTENT parameter support
- Code feedback:
1. The OutputExtentParameter getVariable(int) method should be located above the private methods in... - 05:21 AM Feature #1620: implement EXTENT parameter support
- About the validation clause attached to an extent variable/field and which uses the extent in the validation expressi...
- 03:01 AM Feature #1620: implement EXTENT parameter support
- > Did you resolve the getSourceCodeVersion TRPL error?
No, because the next step would have been to start checking t... - 08:31 PM Feature #1620: implement EXTENT parameter support
- I have reviewed the proposed ruleset changes. They look good. I'll look at the runtime changes tomorrow.
Did you... - 01:10 PM Feature #1608: implement full appserver support (from 4GL clients only)
- I like your approach with the ControlFlowOps APIs....
- 12:57 PM Feature #1608: implement full appserver support (from 4GL clients only)
- Some notes about the RUN statement which targets a remote procedure:
# @RUN PERSISTENT [SET handle] ... ON server@ c...
02/11/2013
- 06:03 PM Feature #1641: implement SAX XML support
- Yes, go ahead and add most of the others. Exclude the following attributes (they are not specific to SAX): ADM-DATA,...
- 04:49 PM Feature #1641: implement SAX XML support
- The testcases has been uploaded. All statements inside are converted and compiled with stubs. I'm preparing Javadoc e...
- 12:48 PM Feature #1620: implement EXTENT parameter support
- > Please provide details of the error.
The warning is in red and it says:... - 11:46 AM Feature #1620: implement EXTENT parameter support
- ...
- 11:40 AM Feature #1620: implement EXTENT parameter support
- Attached update which:
* is merged with bzr revision 10166
* emit ArrayAssigner.lengthOf in case of dynamic-extent ... - 10:58 AM Feature #1979 (Closed): conversion support for DOM XML processing
- 10:54 AM Feature #1639: implement socket support
- Looks good. We will get this into testing soon.
- 10:38 AM Feature #1639: implement socket support
- Must have used a wrong version of language_statements , made the change and converted the tests, everything seems ok ...
- 10:25 AM Feature #1639: implement socket support
- Everything looks OK except you have regressed something in the merge with language_statements.rules. The version the...
- 10:09 AM Feature #1639: implement socket support
- Added update synchronized with latest version
- 08:40 AM Feature #1639: implement socket support
- Eugenie will be checking in an update shortly. You will have at least 2 files to merge. Please do so quickly and th...
- 06:30 AM Feature #1639: implement socket support
- Forgot to modify the module name from history header, when I renamed some of the classes.
- 05:51 AM Feature #1639: implement socket support
- Updated with latest commit from CA.
- 08:58 AM Feature #1640: implement DOM XML support
- The update evl_upd20130206c.zip has been passed the regression testing ans was committed in bzr as 10166.
- 03:33 AM Feature #1884: add some of the v10 data types and core built-ins
- Passed regression testing, committed to bzr revision 10165.
02/09/2013
- 12:34 PM Feature #1620: implement EXTENT parameter support
- Added almost final update which adds support for:
* support for p2j.cfg.xml's new source-code-version (see comments ... - 12:33 PM Feature #1621: implement dynamic/unspecified EXTENT support
- Dynamic-extent variables can not be used as widgets, like @form x with frame f1@ where @def var x as int extent@.
02/08/2013
- 02:34 PM Feature #1608: implement full appserver support (from 4GL clients only)
- ...
- 02:08 PM Feature #1608: implement full appserver support (from 4GL clients only)
- For Server handle the folllowing attributes have types that are not yet implemented...
- 08:37 AM Feature #1608: implement full appserver support (from 4GL clients only)
- Lower priority features:
Server Handle Object methods:
CANCEL-REQUESTS()
CANCEL-REQUESTS-AFTER()
Server Handl... - 01:57 PM Feature #1641: implement SAX XML support
- Actually, you are testing the new longchar data type support right now (in staging). Please map any longchar stuff t...
- 01:27 PM Feature #1641: implement SAX XML support
- One point to clarify:
In some methods I see the LONGCHAR as possible data type for parameters. It is not currently... - 08:42 AM Feature #1991: runtime support for appserver
- This task is just for time tracking. All history should be in the parent task #1608.
- 08:41 AM Feature #1991 (Closed): runtime support for appserver
- 08:41 AM Feature #1990: conversion support for appserver
- This task is just for tracking time and associating the work with milestone 4. All history should be in the parent ta...
- 08:40 AM Feature #1990 (Closed): conversion support for appserver
- 08:26 AM Feature #1639: implement socket support
- Looks good. We will get it into testing shortly.
- 06:33 AM Feature #1639: implement socket support
- Added proposed update(strangely that missplaced "=" sign didn't break conversion), converted previously created tests...
- 04:39 AM Feature #1884: add some of the v10 data types and core built-ins
- Fixed another problem, related to the fact that Text was missing a @Text(Text)@ c'tor, to initialize it properly (@ch...
02/07/2013
- 06:57 PM Feature #1639: implement socket support
- Feedback:
1. methods_attributes.rules has a "stray" equal sign (=) just after prog.kw_set_s_o. I think that would... - 02:10 PM Feature #1639: implement socket support
- Added the proposed update with reviewed issues + superclasses HandleChain and SensitiveResource implementing the comm...
- 12:14 PM Feature #1639: implement socket support
- OK, I like it.
- 12:12 PM Feature #1639: implement socket support
- I took a look at Costin's code and I think it will be a lot easier (and it will provide faster access) if we will mov...
- 11:24 AM Feature #1639: implement socket support
- We at least need a common superclass for Socket and SocketListener so that the code for these attributes (e.g. NAME.....
- 11:17 AM Feature #1639: implement socket support
- > 13. We should have a superclass that can implement PRIVATE-DATA, NAME, TYPE, SENSITIVE... and other common attribut...
- 10:11 AM Feature #1639: implement socket support
- ...
- 09:42 AM Feature #1639: implement socket support
- > 7. I'm not sure why there are changes in widget_references.rules and frame_scoping.rules. I definitely don't want s...
- 05:09 PM Feature #1641: implement SAX XML support
- Just add similar import creation code to the language_statements.rules. It doesn't hurt if the JAST gets more than 1...
- 04:58 PM Feature #1641: implement SAX XML support
- I've found the strange conflict.
1. We need to import .xml.* package to the converted file.
2. It is happening in m... - 04:14 PM Feature #1641: implement SAX XML support
- Excellent, thanks!
- 03:46 PM Feature #1641: implement SAX XML support
- > Everything is good in the plan, except I don't want XmlHelper to be the factory for create statements. Just add the...
- 03:40 PM Feature #1641: implement SAX XML support
- Everything is good in the plan, except I don't want XmlHelper to be the factory for create statements. Just add them...
- 03:32 PM Feature #1641: implement SAX XML support
- Implementation plan:
1. The create statements will refer to static methods in XmlHelper class.
2. The methods and a... - 11:21 AM Feature #1641: implement SAX XML support
- Yes, you're right that SET-NODE is not for SAX. It is for SOAP support. Don't work on it here.
- 11:16 AM Feature #1641: implement SAX XML support
- I have updated the SAX related attributes/methods list. The question for method set-node() you noted. I have not foun...
- 02:04 PM Feature #1620: implement EXTENT parameter support
- I was dropping it because I think it was emitting the extent literal (if present) in the generated code. I will modif...
- 01:58 PM Feature #1620: implement EXTENT parameter support
- OK. My only comment is that generally, I only drop nodes (using the !) that are "syntactic sugar". For example, DOT...
- 01:20 PM Feature #1620: implement EXTENT parameter support
- > So progress.g needs to be updated to support that syntax. If the project code (server or gui) had that construct, ...
- 11:25 AM Feature #1620: implement EXTENT parameter support
- OK.
- 11:19 AM Feature #1620: implement EXTENT parameter support
- To be sure we don't brake anything in MAJIC, we will need to add this flag for this task (IMO, this is a conversion i...
- 10:04 AM Feature #1620: implement EXTENT parameter support
- We are already needing a similar feature for int64 support. v9 compiles some things to integer that v10 compiles to ...
- 09:00 AM Feature #1620: implement EXTENT parameter support
- In convert/variable_definitions.rules, on line 550, it states that all output parameters for functions will initializ...
- 10:47 AM Feature #1963 (Closed): implement conversion support for MEMPTR/RAW
- 10:44 AM Feature #1960 (Closed): conversion support for Windows environment/registry access
- 10:23 AM Feature #1884: add some of the v10 data types and core built-ins
- Update contains P2J fixes for:
# setter for character fields emit as Text
# operator.rules bug
# TextOps.concat re... - 09:29 AM Feature #1884: add some of the v10 data types and core built-ins
- ...
- 07:47 AM Feature #1884: add some of the v10 data types and core built-ins
- Beside the MAJIC-related changes (btw, MAJIC update should be attached here or to #1973?), there are a few other prob...
- 02:04 AM Feature #1884: add some of the v10 data types and core built-ins
- I've fixed the javadoc problems in this update (you are right, no special testing is needed for these changes, as the...
- 08:24 AM Feature #1982 (Closed): conversion support for widget pools
- 01:48 AM Feature #1982 (Review): conversion support for widget pools
- 08:22 AM Feature #1636 (Closed): implement peristent trigger support
- 01:48 AM Feature #1636: implement peristent trigger support
- Regression testing has passed, applied to bzr revision 10162.
- 07:11 AM Feature #1640: implement DOM XML support
- The remaining attribute/methods list has been updated after reviewing the 11.x Progress docs.
- 01:51 AM Feature #1792: implement widget-pool support
- Regression testing for the conversion support update has passed, applied to bzr revision 10162.
- 01:50 AM Feature #1920: implement persistent procedures
- Regression testing of the ca_upd20130131d.zip changes has passed, applied to bzr revision 10162.
02/06/2013
- 05:45 PM Feature #1641: implement SAX XML support
- From our document called "Getting Started with P2J Development":...
- 04:57 PM Feature #1641: implement SAX XML support
- SAX-READER, SAX-WRITER, SAX-ATTRIBUTES Objects:
The already mentioned statements, attributes and methods:
CREATE SA... - 07:58 PM Feature #1641: implement SAX XML support
- Please document the full list of SAX-related features (e.g. everything related to the SAX-attributes/SAX-reader/SAX-w...
- 05:43 PM Feature #1639: implement socket support
- Feedback:
1. The socket_events function in common-progress.rules seems to have the following issues:
a. It assu... - 02:07 PM Feature #1639: implement socket support
- Added proposed update (also includes support for 4GL compiler variables READ-AVAILABLE and READ-EXACT-NUM used for ...
- 04:31 PM Feature #1620: implement EXTENT parameter support
- The good news is that there is no usage of user-defined functions returning an extent in any of the project code. Th...
- 11:47 AM Feature #1620: implement EXTENT parameter support
- # is cleaner to let -1 for non-extent, 0 for dynamic-extent and >0 for fixed-size extent (these constants will be use...
- 08:25 AM Feature #1620: implement EXTENT parameter support
- OK. Do it.
- 05:28 AM Feature #1620: implement EXTENT parameter support
- > It may be time for this. However, I worry about how much development time this will take, since we have a tight sc...
- 02:52 PM Feature #1640: implement DOM XML support
- I have applied it. We will have to rebuild P2J before testing can start.
- 02:14 PM Feature #1640: implement DOM XML support
- Another issue has been found. Please use the recent file. Does not affect the conversion.
- 01:53 PM Feature #1640: implement DOM XML support
- The fix has been uploaded.
- 01:25 PM Feature #1640: implement DOM XML support
- I applied the change to lightning and tried to rebuild P2J. I got these errors:...
- 12:49 PM Feature #1640: implement DOM XML support
- No, don't add the low priority attributes/methods right now.
I am OK with the code as uploaded. It will go into t... - 11:34 AM Feature #1640: implement DOM XML support
- As you can see the amount is more than 10. Do we need them to be added?
- 10:24 AM Feature #1640: implement DOM XML support
- The remaining attributes/methods:
Attributes
CHILD-NUM
ENCODING
HANDLE
INSTANTIATING-PROCEDURE
LOCAL-NAME
NAMESPACE... - 08:19 AM Feature #1640: implement DOM XML support
- Please review the Progress 4GL Reference and make a list of all other DOM XML features which are not listed above. I...
- 12:10 AM Feature #1640: implement DOM XML support
- > 1. Don't we need a getNode() method to match the one in Progress? It should not be removed. It should just return a...
- 02:27 PM Feature #1884: add some of the v10 data types and core built-ins
- I have applied it. There are some compile warnings:
[javac] /mnt/san/sata/gc/20121029/p2j/src/com/goldencode... - 02:04 PM Feature #1884: add some of the v10 data types and core built-ins
- OK, I've made the changes, the update is attached.
- 01:58 PM Feature #1884: add some of the v10 data types and core built-ins
- Just put it in the following:
1. In the TRPL rules where it emits "" as the default.
2. In the class level Javado... - 01:51 PM Feature #1884: add some of the v10 data types and core built-ins
- For byteLength, OK, I've changed the javadoc. But I don't understand what javadoc I should change related to default ...
- 01:47 PM Feature #1884: add some of the v10 data types and core built-ins
- The code changes look good. My only concern is that the issues 1 (default init) and 3 (byte length) should have the ...
- 01:40 PM Feature #1884: add some of the v10 data types and core built-ins
- 1 - although documentation states longchar inits to unknown, practice says different - testing showed that initial va...
- 07:47 PM Feature #1884: add some of the v10 data types and core built-ins
- Feedback:
1. The Progress documentation states that the default initializer for longchar is unknown value. But no... - 11:33 AM Feature #1621: implement dynamic/unspecified EXTENT support
- Once a dynamic-extent array has its size set using the @EXTENT@ statement, a second @EXTENT@ statement on that array ...
- 07:52 PM Feature #1988: runtime support for SAX
- This is a task for time tracking and association of the conversion portion with milestone 4. Put all history in the ...
- 07:52 PM Feature #1988 (Closed): runtime support for SAX
- 07:51 PM Feature #1987: conversion support for SAX
- This is a task for time tracking and association of the conversion portion with milestone 4. Put all history in the ...
- 07:50 PM Feature #1987 (Closed): conversion support for SAX
02/05/2013
- 05:55 PM Feature #1640: implement DOM XML support
- Code feedback:
1. Don't we need a getNode() method to match the one in Progress? It should not be removed. It sh... - 05:24 PM Feature #1640: implement DOM XML support
- The point to discuss:
> 7. I think the runtime implementation is not correct. We don't need to keep a "parallel" tre... - 02:57 PM Feature #1640: implement DOM XML support
- The new drop has been uploaded:
1. The methods/attr relocated in alphabetical order.
2. The rule files have been ... - 11:30 AM Feature #1640: implement DOM XML support
- Feedback:
1. The versions of existing files (like methods_attributes.rules and language_statements.rules) need to ... - 09:03 PM Feature #1640: implement DOM XML support
- The new update has been significantly reworked. Now it completely uses org.w3c.dom classes. The only remaining mappin...
- 04:15 PM Feature #1620: implement EXTENT parameter support
- ...
- 04:08 PM Feature #1621: implement dynamic/unspecified EXTENT support
- ...
- 01:59 PM Feature #1920: implement persistent procedures
- Added an email dispatched to the team:
> If you encounter problems with attributes/methods converting using an incor... - 01:51 PM Feature #1920: implement persistent procedures
- Two cases Vadim has found:...
- 01:32 PM Feature #1920: implement persistent procedures
- I agree chained unwrap and method calls instead of nested unwrap calls will look better, and the change is pretty sim...
- 01:06 PM Feature #1920: implement persistent procedures
- I know that recently we have had some issues related to handle chaining as well as with handle usage as an l-value. ...
- 01:08 PM Feature #1639: implement socket support
- Yes, defer the SELF support for now.
- 01:01 PM Feature #1639: implement socket support
- I will try to get it done tomorrow if SELF support is not needed for sockets at the moment.
- 12:46 PM Feature #1639: implement socket support
- In regard to INSTANTIATING-PROCEDURE, working on that is not urgent right now.
SELF is used in the server project ... - 05:19 AM Feature #1639: implement socket support
- The wait-for loop for socket events exposes another issue related to handles. In 4GL, it is legal something like:
<p...
02/04/2013
- 01:45 PM Feature #1621 (WIP): implement dynamic/unspecified EXTENT support
- 01:40 PM Feature #1621: implement dynamic/unspecified EXTENT support
- Later edit for this statement:
> or, in cases when extent variables are passed to parameters, we should use a simila... - 01:37 PM Feature #1621: implement dynamic/unspecified EXTENT support
- Is there any case in P2J where something like @i = v[1]@ where v is an extent variable gets converted to the Java equ...
- 08:29 AM Feature #1621: implement dynamic/unspecified EXTENT support
- In Openedge 10.x, variables (and fields too?) can be defined as an indeterminate size that is "fixed" at runtime. Th...
- 01:45 PM Feature #1620 (WIP): implement EXTENT parameter support
- 01:40 PM Feature #1620: implement EXTENT parameter support
- > Starting in Progress 10.x extent parameters are allowed in procedures and functions.
The solution is to use Java a... - 08:27 AM Feature #1620: implement EXTENT parameter support
- Starting in Progress 10.x extent parameters are allowed in procedures and functions. Also, function return values ca...
- 01:24 PM Feature #1639: implement socket support
- Remaining Issues:
Event support is implemented at the moment as widgets origin only, I'll have to think a bit more o... - 10:45 AM Feature #1639: implement socket support
- I realized at runtime the same kind of problem happens on the SENSITIVE attribute which is already implemented inside...
- 07:06 AM Feature #1639: implement socket support
- The INSTANTIATING-PROCEDURE doesn't exist in the list of attributes to support for customer project task #1668 so it ...
- 07:08 AM Feature #1884: add some of the v10 data types and core built-ins
- The attached update has the P2J sources merged with bzr revision 10160; javadocs are added, can be reviewed.
02/03/2013
- 06:16 PM Feature #1649: implement Windows environment/registry access
- Bit change to fix log entry number in header. There are no code changes, just wrong number from 008 to 018 fix.
- 08:59 AM Feature #1584: add conversion and runtime support for INT64 and DATETIME data types
- I inadvertently missed a change in my update zip. The following diff is from com/goldencode/p2j/persist/type/DateUse...
02/02/2013
- 04:49 AM Feature #1920: implement persistent procedures
- Conversion regression testing has passed (no changes in the generated sources).
- 04:49 AM Feature #1636: implement peristent trigger support
- Conversion regression testing has passed (no changes in the generated sources).
- 07:15 PM Feature #1640: implement DOM XML support
- The refined code to review with Javadoc and all stubs implemented. However I need to think a bit more on implementati...
02/01/2013
- 03:11 PM Feature #1584: add conversion and runtime support for INT64 and DATETIME data types
- This update fixes a regression found in testing. All timezone initialization changes have been backed out of the dat...
- 01:55 PM Feature #1639: implement socket support
- After testing for the possible handles that can have the argument name the following results:
Handles which suppor... - 08:19 AM Feature #1639: implement socket support
- Yes, do the same analysis on that one too. Please send an email to the entire team about INSTANTIATING-PROCEDURE to ...
- 08:14 AM Feature #1639: implement socket support
- Besides the name attribute there is also an attribute called "INSTANTIATING-PROCEDURE" this appears in both SOCKET an...
- 08:07 AM Feature #1639: implement socket support
- I agree that we need to add some support for setName() as it does seem to be writable. But it is not clear where to ...
- 06:20 AM Feature #1639: implement socket support
- While converting the previously created tests for socket attributes and methods, I encountered the following problem:...
- 01:27 PM Feature #1792: implement widget-pool support
- >1. Do we need to implement a global unnamed widget-pool like Progress does? This would ensure that "proper" deletes ...
- 12:13 PM Feature #1640: implement DOM XML support
- The very fist implementation uploaded. There are no Javadocs, the code is in early state and something is not yet imp...
- 08:23 AM Feature #1920: implement persistent procedures
- Added tests for the subscript and the method chain cases.
- 08:02 AM Feature #1984: make methods to act as "read-only" attributes
- In 4GL, a code which has a method name as a l-value compiles correctly:...
- 08:01 AM Feature #1984 (New): make methods to act as "read-only" attributes
- 07:55 AM Feature #1636 (Review): implement peristent trigger support
- 07:50 AM Feature #1636: implement peristent trigger support
- Attached are testcases and P2J sources which implement both conversion and runtime support for persistent triggers.
Also available in: Atom