RE: XPLNCODE and MSMail

[holmgrn@xxxxxxxx]

> Just to make sure I'm not imagining things, how about resending the
> original post with the full BEGIN line? I'd like to see if the
> problem is reproducible . . . 

Here come two msgs (called #4 and #5), and again I'll just
re-transmit my original msg; the only difference between #4 and
#5 will be that #4 says "begin" while #5 says "b-gin". Assuming
that Carl has indeed divined the problem here (the keyword
"begin"), oh that all programming problems were so easy!

To pursue the thread about casual legibility briefly: If you
leave all the "readability aids" in XPLCODE turned "ON" (the
default), then that little long-jump snippet would normally read:

...{<}SX01,{<}CP{>}{>}...{<}LBA{>}[BX_]jmp {<}PV01{>}[Q2_]{<}
IF{<}CP{>}<>{<}PV01{>}{>}{<}GLA{>}{<}EI{>}...[cr|lf]

Note that there are three sets of "readability aids": a
customization table (e.g. turns {174} into {<}, or [13+10] into
[cr|lf]), a function table (turns [255+130+171] into [BX_]), and
an extended character table
(turns [254+154+1] into extended character [666]). You can
enable|disable each of the three aids individually. Enabled,
code is easy-to-read.
Unfortunately, you can't be sure that the recipient's
customization table is identical to the sender's. Neither can
you be sure that the sender drew a distinction (if even aware of
a distinction) between
(for example) {13} {10} [13+10] or [10+13]. With all the aids
turned OFF
(as I routinely have them, for max hands-off accuracy), you get
the code that we've been discussing hitherto:

...{174}SX01,{174}CP{175}{175}...{174}LBA{175}[255+130+171]jm p
{174}PV01{175}[255+130+127]{174}IF{174}CP{175}<>{174}PV01{1
75}{175}{174}GLA{175}{174}EI{175}...[13+10]

Trade-offs. Then again, here's XXBUG:

n9WsifZBMA12gfYBEfuwi9WuiH27-fzy0eqdhQ00iI3MkAOzzUbyiGIOiEp0jD1uiI3Mk
GAOyjfYRAEOyiFIaj9Wsi1EcO

Oh well.

------------
Robert J. Holmgren holmgrn@xxxxxxxx
------------