Re: XPL questions

[Carl Distefano cld@xxxxxxxx]

Reply to note from "Robert Holmgren"  Sun, 3
Sep 2006 00:09:30 -0400

> > To explain this behavior, all I can think of is that {CR} is
> actually two bytes. But if you SEarch for just not-
> CarriageReturn, CarriageReturn, it works as expected.
>
> The two bytes is key. SEarch for {not}{cr} by itself, and it
> jumps two bytes.

Interesting little bug. In Harry's example, it's easy enough to
work around: BX se "[w-][wC][wC][w-][wC]"Q2 )>CL 

In DECODEable XPL:

XPLeNCODE v2.0
b-gin [UNTITLED]
[BX_]se "[w-][wC][wC][w-][wC]"[Q2_]{<}IF@not({<}ER{>}){>}[CL_
]{<}EI{>}[cr|lf]
-nd
XPLeNCODE

BTW, the "not" wildcard bombs with 3-byte characters. For example,
BX se "[w-]BC "Q2 flags func BC, and BX se "[w-][255+54+49]"Q2 flags
a 3-byte "a" -- in each case, the very character the command is
meant to skip.

--
Carl Distefano
cld@xxxxxxxx