XPL is smarter than we are

[Harry Binswanger hb@xxxxxxxx]

Earlier I asked about how to re-set the error flag. I
thought I needed it for a conditional search--i.e., a search done if a
previous search came up "Not found." I assumed that the
"Not found" error flag (va $er = 10)  would stay set
unless I forced it to some other value. But it turns out that even though
va/nv $er shows that the error flag is still 10, it isn't
operative.



That is, I that the below gave the desired response when searching
through a file that did not have the first string ("xxxxx") but
did have the second ("a").



XPLeNCODE v2.0

b-gin [UNTITLED]

[BX_]se /xxxxx/[Q2_]{<}IF{<}ER{>}{>}[BX_]se
/a/[Q2_]{<}EI{>};

*;[cr|lf]{<}IF{<}ER{>}{>}[BC_]I'm coming up as an
error{<}GL,

A{>}{<}EI{>};*;[cr|lf][BC_]no error here--I got found
it[GT_]

{<}LB,A{>}{<}EX{>}[cr|lf]

-nd

XPLeNCODE



But doing a va/nv $er after it runs still shows 10.









Harry Binswanger
hb@xxxxxxxx