FWD » Core Development » Conversion Tools

04/01/2017

12:58 PM Feature #1521: implement gap analysis rules or backing database/marker approach

> So the background to describe the support level is detailing investigation of the convert/expressions.rules, corre... Greg Shah

08:34 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Thinking about the way to find out the support status info for expression related keywords. Looks like the simple sea... Eugenie Lyzenko

03/31/2017

03:21 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> These are known as "compiler constants" and having predefined values(0,1,2,...).
Yes.
> This means all of the... Greg Shah

03/30/2017

07:25 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
> > Add to existed marking for literals?
>
> Yes, just add them to the map of literals. Why do ... Eugenie Lyzenko

03:52 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
> Ignore FILENAME, in expressions it needs no marking.
>
> @COLON@ needs to be handled. It shou... Eugenie Lyzenko

03:43 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Ignore FILENAME, in expressions it needs no marking.
@COLON@ needs to be handled. It should be handled on its own... Greg Shah

03:23 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Updated and fixed keywords distribution into the groups:
@fields@
FIELD_BLOB
FIELD_CHAR
FIELD_CLASS
FIELD_CLOB... Eugenie Lyzenko

03:14 PM Feature #1521: implement gap analysis rules or backing database/marker approach

>> Add to existed marking fro literals?
>Yes, just add them to the map of literals. Why do anything else?
OK. Eugenie Lyzenko

03:12 PM Feature #1521: implement gap analysis rules or backing database/marker approach

> Add to existed marking fro literals?
Yes, just add them to the map of literals. Why do anything else?
> It ... Greg Shah

03:08 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
> > KW_FIND_CS
> > KW_FIND_GLO
> > KW_FIND_NO
> > KW_FIND_PO
> > KW_FIND_WA
> > KW_WIN_DMIN
>... Eugenie Lyzenko

01:21 PM Feature #1521: implement gap analysis rules or backing database/marker approach

> KW_AVG
> KW_COUNT
> KW_MAX
> KW_MIN
> KW_SUM
These are already handled.
> MULTIPLY
This is handled tod... Greg Shah

12:46 PM Feature #1521: implement gap analysis rules or backing database/marker approach

I have added @primary_expr@ with these sub-rules into general @expr@ schema. As to "unusual" built-in functions, almo... Eugenie Lyzenko

08:21 AM Feature #1521: implement gap analysis rules or backing database/marker approach

>> I thought this was replaced with SYMBOL:
> ... Greg Shah

07:40 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
> What about DB_REF_NON_STATIC?
I thought this was replaced with @SYMBOL@:... Eugenie Lyzenko

03:48 AM Feature #1521: implement gap analysis rules or backing database/marker approach

What about DB_REF_NON_STATIC? Greg Shah

03:47 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Did you check to see if we are marking all of the "unusual" built-in functions properly? Here is a list:
sql_aggr... Greg Shah

03:47 AM Feature #1521: implement gap analysis rules or backing database/marker approach

I think that @primary_expr@ is missing from the @expr@ call tree in #1521-153. Have you handled all of these cases? Greg Shah

03:41 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> KW_BETWEEN
> KW_BY_PTR
> KW_BY_VAR_P
> KW_IS
These are not variables. All variables are VAR_ only. Please l... Greg Shah

10:15 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Here is the expressions related keywords distributed to the respective groups. We can create either single file for a... Eugenie Lyzenko

03/29/2017

03:51 PM Feature #1521: implement gap analysis rules or backing database/marker approach

The candidate list in note #149 has been updated based on recent research. Start separating the keywords for standalo... Eugenie Lyzenko

02:51 PM Feature #1521: implement gap analysis rules or backing database/marker approach

This is the complete @expr@ rules tree:... Eugenie Lyzenko

08:53 PM Feature #1521: implement gap analysis rules or backing database/marker approach

New keywords to process:... Eugenie Lyzenko

03/28/2017

05:34 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> The question for UNKNOWN_TOKEN. This special artificial keyword means the detected keyword behind is not registered... Greg Shah

03/27/2017

05:04 PM Feature #1521: implement gap analysis rules or backing database/marker approach

I have checked once again all already marked categories in @gaps/gap_analysis_marking.xml@ and have not found somethi... Eugenie Lyzenko

09:11 AM Feature #1521: implement gap analysis rules or backing database/marker approach

The candidate list for expression related keywords to add:... Eugenie Lyzenko

03/24/2017

04:38 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
> > There are two more double items found for built-in functions:
>
> Fix those in 1521c.
Don... Eugenie Lyzenko

03:03 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Created task branch @1521c@ from trunk revision @11144@. Eugenie Lyzenko

11:00 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> There are two more double items found for built-in functions:
Fix those in 1521c. Greg Shah

11:00 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> The remaining FUNC_ that are not marked are:
> ...
> Correct?
No. We already mark any FUNC_ type that is mar... Greg Shah

10:54 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
>
> By the way, we already handle all the @FUNC_@ types that are marked as "builtin". The non-bu... Eugenie Lyzenko

08:24 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> General gap concept question. We need to enumerate all possible keywords and put them in a separate groups by some ... Greg Shah

12:25 AM Feature #1521: implement gap analysis rules or backing database/marker approach

New expression related(direct or indirect from @9th and highest precedence level of Progress 4GL expressions@) keywor... Eugenie Lyzenko

03/23/2017

04:57 PM Feature #1521: implement gap analysis rules or backing database/marker approach

I checked in "Made 'all' build target depend on 'distribution' target." to 1521b revision 11149. Hynek Cihlar

04:17 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Fixed. Greg Shah

04:05 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg,
Checking the keywords for already handled status I found small issue in @gaps/expression.rules@ file:... Eugenie Lyzenko

01:29 PM Feature #1521: implement gap analysis rules or backing database/marker approach

1521b is frozen at this time. Eric is putting it through conversion regression testing. It has no runtime implicati... Greg Shah

07:38 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> What about 9th and highest precendence level of Progress 4GL expressions? Do we need to consider the cases included... Greg Shah

03/22/2017

05:50 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
> Most of the token types in your list are already handled by the operators list in @gaps/expressio... Eugenie Lyzenko

09:02 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Most of the token types in your list are already handled by the operators list in @gaps/expressions.rules@, right?
... Greg Shah

10:01 PM Feature #1521: implement gap analysis rules or backing database/marker approach

The keywords extracted from different kind of expressions(in @progress.g@):... Eugenie Lyzenko

03/21/2017

06:51 AM Feature #1521: implement gap analysis rules or backing database/marker approach

I want you to focus on the @expr@ rule in @progress.g@. Do not worry about @convert/expression.rules@.
> I have a... Greg Shah

10:24 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Studied the task objective. Correct me if I'm wrong. I have scanned @convert/expression.rules@ and found the candidat... Eugenie Lyzenko

03/15/2017

09:58 AM Feature #3265: enhance pphints to have references, expansions and details in and about directives

The pphints mechanism was deliberately implemented to only contain information regarding code that exists in the full... Greg Shah

09:52 AM Feature #3265 (New): enhance pphints to have references, expansions and details in and about dire...

Greg Shah

09:50 AM Bug #3256 (Closed): comments disappear inside strings when the preprocessor evaluates expressions

3255a was merged to trunk as revision 11143. Greg Shah

03/14/2017

01:57 PM Bug #3242 (Closed): parser console output written out of order

Additional changes were applied by ECF in branch 3255a, which was merged to trunk as revision 11143. At this time, a... Greg Shah

11:18 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
> Yes.
>
> I'm doing the final cleanup on language statements. Consider that complete.
>
> I... Eugenie Lyzenko

11:17 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Yes.
I'm doing the final cleanup on language statements. Consider that complete.
I'll let you know the next pr... Greg Shah

11:10 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
> I've created task branch 1521b from trunk 11143.
So any further updated for this task will be ... Eugenie Lyzenko

09:20 AM Feature #1521: implement gap analysis rules or backing database/marker approach

I've created task branch 1521b from trunk 11143. Greg Shah

09:19 AM Feature #1521: implement gap analysis rules or backing database/marker approach

ETF testing passed. Re-run of reporting was successful. Testing is complete.
3255a has been merged to trunk as ... Greg Shah

05:59 AM Feature #1521: implement gap analysis rules or backing database/marker approach

3255a branch revision 11145 passed ChUI regression testing. The conversion result was identical with trunk. The run... Greg Shah

03/13/2017

03:21 PM Feature #1521: implement gap analysis rules or backing database/marker approach

3255a is locked for regression testing. I'm going to test using rev 11145. Greg Shah

12:20 PM Feature #1521: implement gap analysis rules or backing database/marker approach

No, this is because we built this from a combination of 1521a and 3209e. Then a later version of 3209e was merged to... Greg Shah

12:12 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
> 3255a has been "rebased" from trunk 11142. The rebase process is broken for this branch so I had... Eugenie Lyzenko

11:07 AM Feature #1521: implement gap analysis rules or backing database/marker approach

3255a has been "rebased" from trunk 11142. The rebase process is broken for this branch so I had to merge. The late... Greg Shah

10:47 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> You mean for example the cases like:
> ...
> We need to include only:
...
> And NOT to include:
...
> becuse ... Greg Shah

09:46 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
> Code Review Task Branch 3255a Revision 11147
>
> This was a good start, but there were many er... Eugenie Lyzenko

09:24 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Code Review Task Branch 3255a Revision 11147
This was a good start, but there were many errors. Some problems wer... Greg Shah

03/11/2017

09:58 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Task branch @3255a@ for review updated to revision @11147@.
Finishing import the language statements from @progres... Eugenie Lyzenko

03/10/2017

05:38 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> I have not found KW_BLK_LVL keyword(block_level_stmt in progress.g). This keyword does not have the statement?
... Greg Shah

09:41 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Task branch @3255a@ for review updated to revision @11144@.
Importing language statements from @progress.g@ file. ... Eugenie Lyzenko

03/09/2017

01:51 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Code Review Task Branch 1521a Revision 11143
1. @put-bits@ is fully supported. It is not part of @memptr@. It is... Greg Shah

03/08/2017

05:04 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Task branch @3255a@ for review updated to revision @11143@.
This is the first step for iterative creation of the l... Eugenie Lyzenko

03/07/2017

11:56 AM Feature #1521: implement gap analysis rules or backing database/marker approach

3255a is now based on trunk revision 11141. I could not use the normal rebase process since this branch was composed... Greg Shah

11:26 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Consider 3255a locked. I am rebasing it right now. Greg Shah

11:13 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Please create @lang_stmts.rules@. Language statements cover all areas.
To see the matching criteria, look at the ... Greg Shah

11:02 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
> Eugenie: your next task is to encode marking rules for the following:
>
> * language statement... Eugenie Lyzenko

08:35 AM Feature #1521: implement gap analysis rules or backing database/marker approach

I will do this shortly. Greg Shah

08:08 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
> Put the changes in 3255a. Please make sure you don't break anything with your check-ins, because... Eugenie Lyzenko

07:40 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Put the changes in 3255a. Please make sure you don't break anything with your check-ins, because others are working ... Greg Shah

07:33 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
> Eugenie: your next task is to encode marking rules for the following:
>
> * language statement... Eugenie Lyzenko

07:27 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Eugenie: your next task is to encode marking rules for the following:
* language statements (we just need to mark ... Greg Shah

07:18 AM Feature #1521: implement gap analysis rules or backing database/marker approach

1521a has been archived.
3255a contains a large number of improvements including some cleanup of the frame/browse/... Greg Shah

03/06/2017

09:24 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
> The latest version of 1521a is 11164. I have merged this into 3255a. Please do NOT do any addit... Eugenie Lyzenko

03/04/2017

12:09 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
> The latest version of 1521a is 11164. I have merged this into 3255a. Please do NOT do any addit... Eugenie Lyzenko

10:34 AM Feature #1521: implement gap analysis rules or backing database/marker approach

The latest version of 1521a is 11164. I have merged this into 3255a. Please do NOT do any additional development on... Greg Shah