Kbase P176219: Compile error 247 when compiling code that is known to be correct.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/28/2010 |
|
Status: Unverified
SYMPTOM(s):
Compile error 247 when compiling code that is known to be correct.
** Unable to understand after -- "<string>". (247)
** Unable to understand after -- "=". (247)
** <program> Could not understand line <number>. (196)
** C:\OpenEdge\WRK\myProcedure.p Could not understand line 2. (196)
FACT(s) (Environment):
Code previously compiled correctly.
Code has not been changed since successful compile
Code is compiled on the fly and executed.
Code is run from another procedure that passes it a preprocessor variable value as an argument.
All Supported Operating Systems
Progress/OpenEdge Product Family
OpenEdge Category: Language (4GL/ABL)
CAUSE:
Another version of the calling procedure exists higher on the PROPATH than the intended version. This version does not set the preprocessor variable. When the called procedure is run, the preprocessor reference is therefore replaced by an empty string. The resulting statement is not syntactically valid, and therefore generates compile error 247.
FIX:
If unexpected compile errors, especially general syntax errors such as error 247 or error 196, are generated by a procedure containing argument references and/or preprocessor variables, check whether the argument references and/or preprocessor variables are being set correctly.