Bhaskar,
Thanks for the help.
When I did a zshow *, it showed the variable table.
Surprisingly, there was no 'T' defined. Would this
cause such an error?
What would extra trailing characters look like in a
string?
Kevin
--- Bhaskar, KS [EMAIL PROTECTED] wrote:
Kevin --
From the GT.M
Kevin --
The error is a compilation error, not a run time error. Had there been
no T, but clean M code to compile, there would have been a different
error - %GTM-E-UNDEF, Undefined local variable: T - rather than the
INDEXTRACHARS you saw.
You can print the string to look for extra
You could actually set X to 2 like this
S X1=(1+1)
S @(X=_X1)
This is a use of indirection that looks a bit odd, because it is
being applied to a string built on the fly, and the string evaluates
to the argument of the command (SET).
===
Gregory Woodhouse
[EMAIL PROTECTED]
Before one gets
curiouser and curiouser... :-)
thanks
Kevin
p.s.
I have tried several times to include a zshow * that
dumps the symbol table. But my Yahoo mail sees it as
spam and rejects it.. Oh well.
Kevin
--- Gregory Woodhouse
[EMAIL PROTECTED] wrote:
You could actually set X to 2 like this
S
Kevin,
I can't help much with the errors, though it looks like you already have
some good advice. My disclaimer is I am far from a purist, and use ScreenMan
to do some pretty easy jobs - like create, edit, and save data.
If you haven't I would suggest XQEDTOPT as an ideal ScreenForm to work
Ironically, my code seems to some people to be littered with @
signs, but this is a kind of indirection I almost never use. It can
be useful in some scenarios, though, as in initializing variables
using lines retrieved from $TEXT (or even from a global).
===
Gregory Woodhouse
[EMAIL
Kevin --
From the GT.M Messages and Recovery Procedures Manual:
--
INDEXTRACHARS
INDEXTRACHARS, Indirection string contains extra trailing
characters
Compile Time Error: This indicates that an indirection string ends with a
syntactically incorrect sequence.
Reading over this, I would suspect that a line in a table has a space
after it. Specifically, the code you are reading is looking at tables
MAP^DDFG0, SMAP^DDFG0, and DMAP^DDFG0.
One of the lines has (in the second piece) some non-MUMPS expression syntax
in the second piece.
Indeed, when I look
