Code Analyst Alternate Rules

Topics: General
Developer
Nov 5, 2008 at 5:11 PM
Edited Nov 5, 2008 at 5:14 PM
In talking with Andrew MacNeill about a process we are going to have to address at some time (forced by corporate forces) to migrate applications to a "Main Stream" language, we have started developing some business standards, rules, to make the future process easier, as well as force us to code better.

I guess I would call the Portability Rules. These Portability Rules will be an Alternate set of Rules for use with the Code Analyst. Using an Alternate Set of rules is an upcoming enhancement that will be added to the Code Analyst.

I will be working on these and would like your feed back of what type of rules you would like to see in the Portability Rules definitions.

examples...
Use of PUBLIC Vars, Warn that these should be properties
SET Procedure, Warn that a Class could be used instead
DEFINE WINDOW, Warn that these are just bad and a Form Class or Object should be used instead

What are your ideas, rules, suggestions?

Happy Foxing!
cj...

Feb 15, 2009 at 4:45 PM
Procedures and functions are ok, you can't place a class method into a select command for example ..