Kbase P161521: 4GL/ABL: Why are we not getting compilation errors if we define a local variable as mtime?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/9/2010 |
|
Status: Unverified
GOAL:
4GL/ABL: Why are we not getting compilation errors if we define a local variable as mtime?
GOAL:
Was there a change in OpenEdge 10.2B that allows variable names to be the same as some keywords?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.2B
FIX:
No compilation errors are generated when 4GL/ABL variables are defined using the same name as some keywords is due to the fact that OpenEdge 10.2B introduced enhancements to minimize name collision and allow some keywords to be used as variable names, class names or temp table names.
This enhancement was introduced in OpenEdge 10.2B to reduce naming collisions between temp-tables, variables, etc. within a class or a procedure.
This change makes porting of existing procedural applications to OOABL applications easier. Customers that have existing procedural code which makes use of the unique namespaces, i.e. having variables, temp-tables, datasets etc. with the same name as some keywords, will not be forced to rename all of their existing data members when changing their code to OOABL.
For more details, see the OpenEdge 10.2B "OpenEdge Getting Started: New and Revised Features" manual.