I belatedly discovered this after writing some code intended for use
with SOUPER, and assuming the format would be the same as UQWK and
Yarn use. The software ran as intended when tested on a *.msg file
created by UQWK, but broke when tested on a *.msg file created by
Souper95.
Is there any way to force Souper95 to create b type files? Reading a
length N and grabbing N bytes seems preferable to parsing the file
and looking for the next "From " at beginning of line. More
importantly, my code must create packets compatible with the type b
files that Yarn creates in replies, so it will have to convert the
incoming type u *.msg to type b *.msg. Not a big deal, but I'd rather
have a single *.msg file type.
I suppose Chin had a good reason to switch formats when he wrote
Souper. Anyone have any idea what it was?
-rex