Re: Programming oddity

[cld@xxxxxxxx (Carl Distefano)]

Reply to note from Patricia M Godfrey  Sat, 19
Feb 2005 19:09:42 -0500

> What happened to the fourth value of L0 in the second
> iteration?

You're not using XS correctly. The second S/G in the series (02)
has to have the parsing separator (the comma)! But you never save
"," to 02 with . As a result, both XS statements do nothing
-- or worse. The second XS statement () is
causing S/G 04 to be overwritten (emptied). Therefore, later, when
you do , you get... nothing.

But, Patricia, both of those XS statements are unnecessary! You're
mushing together two different methods of parsing. All the parsing
you need in this routine is done in , , etc. In
fact, you don't even need VA@. DECODE this, and display it, first,
in Draft view. Pretty neat, huh? Then toggle into eXPanded view.
See what's going on? VAs have their own built-in parsing mechanism.
It works on any VA with multiple values (, , ,
etc. etc.). That Dave Erickson thought of everything.

XPLeNCODE v2.0
b-gin [UNTITLED]
Values in L0, Action Bar:[cr|lf]{tab}Items are {<}VAL01{>}[cr
|lf]{tab}Highlighted items are {<}VAL02{>}[cr|lf]{tab}Acceler
ator character is {<}VAL03{>}[cr|lf]{tab}Background is {<}VAL
04{>}[cr|lf]Values in L1, Command Line Colors:[cr|lf]{tab}Cur
rent path is {<}VAL11{>}[cr|lf]{tab}Typed text is {<}VAL12{>}
[cr|lf]{tab}Wild cards are {<}VAL13{>}[cr|lf]{tab}Function ca
lls are {<}VAL14{>}[cr|lf][cr|lf]
-nd
XPLeNCODE

--
Carl Distefano
cld@xxxxxxxx