Activity
From 02/15/2017 to 03/16/2017
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...
- 09:52 AM Feature #3265 (New): enhance pphints to have references, expansions and details in and about dire...
- 09:50 AM Bug #3256 (Closed): comments disappear inside strings when the preprocessor evaluates expressions
- 3255a was merged to trunk as revision 11143.
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...
- 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... - 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... - 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 ... - 09:20 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- I've created task branch 1521b from trunk 11143.
- 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 ... - 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...
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.
- 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...
- 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... - 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...
- 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 ... - 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... - 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...
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...
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?
... - 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. ...
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...
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...
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...
- 11:26 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Consider 3255a locked. I am rebasing it right now.
- 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 ... - 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... - 08:35 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- I will do this shortly.
- 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... - 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 ...
- 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... - 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 ... - 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/...
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...
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... - 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...
03/03/2017
- 07:33 PM Bug #3256: comments disappear inside strings when the preprocessor evaluates expressions
- This is fixed in 3255a revision 11223.
03/02/2017
- 04:19 PM Bug #3256: comments disappear inside strings when the preprocessor evaluates expressions
- The following program (see @testcases/uast/comments_disappear_inside_strings_when_the_preprocessor_evaluates_expressi...
- 04:15 PM Bug #3256 (Closed): comments disappear inside strings when the preprocessor evaluates expressions
02/17/2017
- 08:29 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11163@.
Adding changes in @gap_analysis_marking.xml@ to:
1. E... - 06:12 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- > If the mark has been found on some step -> we can ignore further steps, saving CPU time, like this:
Good idea.
... - 07:42 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11162@.
In this update the global variables and built-in funct...
02/16/2017
- 03:47 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11161@.
Preparing candidate for global variables and built-in ... - 01:09 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> > And I have reviewed the changes in 3209e since this merge. Do you think something is missed?
>... - 12:21 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- > And I have reviewed the changes in 3209e since this merge. Do you think something is missed?
Yes, I think there ... - 12:18 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> Yes, please go ahead with adding all of these, including the webspeed functions. Treat the websp... - 05:03 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Yes, please go ahead with adding all of these, including the webspeed functions. Treat the webspeed functions just l...
- 10:33 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- The new candidates for built-in functions to add into @expressions.rules@ map:...
- 09:17 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> Please fix @progress.g@ for @_msg@.
OK. Task branch @1521a@ for review updated to revision @11... - 08:48 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Please fix @progress.g@ for @_msg@.
- 08:41 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Good catch. I think this:...
- 07:44 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- OK. According to my refresh for variable/built-in functions criteria the @SUPER(kw_super)@ is the function, not varia...
02/15/2017
- 04:57 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11158@.
Fix removing function and system handles from global v... - 10:58 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- If they have FUNC_ types they are not treated as global variables.
- 10:10 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- >Please go back through your list of questions and make sure you only include VAR_ token types that are not system ha...
- 09:59 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Global variables are matched (see @profile.rpt@) using the @builtin_global_variables@ rule from @common-progress.rule...
- 09:19 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Several questions for handling built-in functions. The conversion support is performing in @convert/builtin_functions...
Also available in: Atom