Reforwarded in case the date caused mail processors upstream to junk the
message due to it being too far in the future:

* Forwarded from fidosoft.husky by andrew clarke (3:633/267{at}fidonet).
* Originally by: andrew clarke (3:633/267), 10 May 28 13:27.
* Originally to: All (0/0).

---------- Forwarded message ----------
After a lot of work, my modifications to the SMAPI are progressing. I've
got it compiling under all the Win32 compilers I mentioned a while ago,
even lcc-win32.  I've also tested them all with sqconver.c (modified to
support JAM), and all are working, except the api_jam.c code is still
broken, and the MingW32 version has a bug in locking.c code which I can
only put down to the MingW32 libraries, and I don't know how to fix.

Among the things I've noticed are that there is a lot of unused code in the
SMAPI, eg. patmat() is only used in one place in the UNIX parts of ffind.c,
and nowhere on any of the other platforms.  So it should really just be a
static function in the UNIX code and not actually exported. But the problem
with this is that hpt (and fidoconf, and probably others, but notably NOT
Msged) assume patmat.h and patmat() are part of the SMAPI, which is a bad
assumption to make, because it's not actually mentioned in the MSGAPI
documentation.  It's either a carryover from the Maximus 2.0 code base, or
was added there much later by someone who just wanted to port the thing and
didn't care about useability and namespace pollution too much.  The same
can be said for Strip_Trailing() and I think some other functions.  If you
want those in HPT, you should supply the code yourself and not assume it
will be in the SMAPI.  This should only mean a few small changes to your
code, ie. rip out the functions yo
u need from the SMAPI and make the modules yourself.  Or just keep using
the SMAPI and stay clear of XMSGAPI, up to you.

I decided to rename my modified SMAPI code to XMSGAPI because originally
when I named SMAPI (in 1997 or whenever it was) it meant "Modified
Squish API", but I couldn't call it MSAPI, because then it looked like
something released by Microsoft. ;-)  But now that it has support (albeit,
still somewhat broken) for JAM bases, not to mention *.MSG (which everyone
forgets about!), and not just Squish, I thought it should be given a new
name.  So XMSGAPI it is, for "eXtended MsgAPI". That is, unless
anyone can think of something better, and I'll call it that.  ;-)

Regards
Andrew

-- mail{at}ozzmosis.com

-+- Msged/NT 6.1.1
 + Origin: Blizzard of Ozz, Mt Eliza, Victoria, Australia (3:633/267)

--- Msged/NT 6.1.1