Fri 2003-05-30 10:32, Wes Garland (1:106/2000) wrote to All:

 WG>  - I now have admin access on SourceForge, we need to get the maximus code up
 WG> there before we have a million trees on the go. I'll see what I can do this
 WG> weekend; my schedule has been a little more hectic this week than
 WG> planned, which means I haven't done much to Max in the last few days. I
 WG> haven't used CVS before, but I'm sure I can figure it out.

Great.  I've e-mailed you my "quick-start" notes on using CVS.

 WG>  - I had a quick chat with Scott. According to him, he doesn't think he
 WG> changed the msgapi binary format or API from version 1.02 to 3.02; he
 WG> said the primary changes (that he could recall) were performance-related.

That's correct.

 WG> This means it might be possible to drop in SMAPI/XMSGAPI (or whatever
 WG> it's called -- you know what I mean) in its place. I'd be tempted to not
 WG> be too quick to do this, however, as there may be some hidden subtleties
 WG> in Maximus that depend on non-obvious msgapi behaviour. I think we're
 WG> better off getting the current product stable before we start grafting 
 WG> stuff on. That said, it does sound like a very good idea, is obviously a
 WG> great place to do code comparisons from.

Yep - I agree with all of this.

 WG> MEX binaries may or may not be cross platform. I'd like them to be, but
 WG> pointer size issues may preclude compatibility on 64-bit architectures.
 WG> Well, okay, *inconvenience* compatibility on 64-bit arches. :)

This is only an issue where the MEX source isn't available.  I'm not sure
that's very common, but if it is, perhaps it may be possible to decompile
the old MEX binaries to the point where they can be recompiled to use
64-bit pointers.  Or if it's simple enough just rewrite it.  ;-)

-- mail{at}ozzmosis.com

--- timEd/FreeBSD 1.11.b1