Project

General

Profile

Feature #2256

create tools to analyze the .pphints files

Added by Constantin Asofiei over 12 years ago. Updated over 9 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
03/12/2014
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

History

#1 Updated by Constantin Asofiei over 12 years ago

From #2251 note 46:

On a side note, there are cases in the server project where there are typos in the preprocessor, like in {a.i &aaa "bla"}, when it should have been {a.i &aaa = "bla"}. Currently, we throw exception in PreprocessorHints.createArgument:922, as the value for this aaa argument is missing. I think we need some tools to analyze the .p.pphints files and check for problems...

The idea for this task is to go through the .pphints files and find if there are not-used and/or not-initialized arguments. The results from this tool needs to be reviewed, to confirm real problems in the 4GL code.

#2 Updated by Greg Shah over 9 years ago

  • Target version deleted (Code Improvements)

Also available in: Atom PDF