KS> Now for a question that's sure to show my ignorance of Fernwood: How's
 KS> that work?

Send it to Emmitt Dove,  and ask him to place it in there.  I can try,but I
not sure how far the files I place in make it.

Emmitt Dove: 1:141/209,
        Fernwood - OS/2! Line 2
        Branford CT,
        Emmitt Dove,
        1-203-481-7934,9600,CM,H16,V34,XA

 >      1) The source code for everything that is required to link the

 KS> didn't like too much about Guidelines, was all of those calls to a
 KS> mysterious set of "Gui" this and that functions that I
didn't find any
 KS> source for.

_exactly_.

 KS> I'm getting ready to buy another compiler, just for that purpose.
 KS> Watcom's price looks like the best, and hopefully it will run on this
 KS> "puny" 8-meg machine. I'd get IBM C/Set++, but I would need a
 KS> supercollider to run the blasted thing, from what I'm told.

If you are extensively using C++ (for example,  you are using ICLUI), an
8MB machine will swap so much it will take a looooooooong time to compile
your stuff.  IBM Cset++,  just for C,  or for smallish C++ will work okay
in 8mb.   Watcom shouldn't have any problem at all.

Don't believe all of the horror stories you hear about IBM Cset++,  it is
not always that slow -- When doing my compiler review,  cset++ was FASTER
than borland when compiling small C files,  with optimization turned on. 
Granted,  it most often swings quite far in the other direction,  but
Cset++ is much better than Cset/2.

Anyway,  I think someone who judges a compiler on how fast it
compiles,instead of how stable the compiled code is,  looks pretty foolish.


 >        Therefore,  it is best to have all of the functions you wish to
 >        export from a LIB/DLL prototyped with something that overrides
 >        the default calling convention.  For 
 > example,  you could use the
 >        EXPENTRY define.

 KS> The problem I see here is with mangled names. How does one do that? 
 KS> "class  EXPORT EXPENTRY MyClass"?  That doesn't work, does it?

I wasn't thinking C++ when I said that.  Short of using SOM,  there is no
way to export a c++ class from one compiler,  to be used with another; 
you'll have to include a DLL for each compiler (and,  in many cases,  for
each VERSION of the compiler).

For the short term,  I'd just ship lots of DLL's.  Soon,  all of the major
compilers should be supporting DTS (direct to som),  which will make them
all plug-and-play.



--- Maximus/2 2.02p1