Compilation fails without feedback for illegal variable name
Brought to you by:
ferret1964,
twiechmann
Menu
▾
▴
#104 Compilation fails without feedback for illegal variable name
If a method is written (by, say, a C programmer ;) with a
parameter variable named with an underscore character,
ESI Objects 4.1.1.1 will "pretend" to compile the method.
No errors or no warnings are generated, but (on a GT.M
platform in this case) no object or even source code is
generated in the /usr/local/esiobjects/user directory.
If an attempt is then made to call the afflicted method an
extremely unintuitive message is returned, which is in
fact complaining about the missing object file.
This problem has only been witnessed with an illegal P%
variable name (P%bit_op, to be precise) but may very
well appear with any variable name if the same, generic
error-checking algorithm is used to detect illegal variable
names.
Logged In: YES
user_id=84471
The attached VESOIM5.rsa file contains a routine that fixes
this problem. Log into the ESI area on your M server and
import the file using the Routine Save utility.
Compiler Routine