rc>> Watcom passes by registers usually?? That's damn strange for a
rc>> HLL. Maybe it's half decent, even.

PE> Yes, it does.

rc>     How do you specify which registers pass which parameters? What if you 
rc> run out of registers?

It uses AX-DX and the rest go on the stack.

rc>     So it's still in there? I can have a peek and suggest routines which 
rc> don't need it, although it's hardly going to decrease the size of the EXE 
rc> by that much.

Actually, I have yet to try it, but I think I have it sussed, I
just need to declare all my assembler routines as cdecl instead 
of normal.

rc>     Interesting, since all the other HLL compilers (QuickBASIC, QuickC, 
rc> Borland Pascal, Borland C?) I have seen use stack based variables, and that 
rc> seems to be the convention. Shouldn't register based parameters be an 
rc> *exception* rather?

I would have expected so.  In their OS/2 compiler you get to choose.

PE>   BTW, I bought the CDROM version of Watcom, which doesn't come with
PE> printed manuals, for a cost of around $300. For that price you get
PE> 16-bit DOS, 16-bit OS/2, 16-bit Windows, 32-bit DOS, 32-bit OS/2,
PE> 32-bit Windows, 32-bit Windows-NT.  BFN.

rc>     So... any plans for a 'doze version of msged ?

I don't believe it is possible to do that without changing the
way the program looks.  If you have a look, there is an IBMSCRN.C
and an OS2SCR.C.  The first is DOS, the second is OS/2.  If it 
were possible to create a third, which was Windows, then it might
be feasible.  From my understanding of Windows, there's no chance
of a simple rewrite of the screen handling to make that work.
If you know better, I'm all ears.  BFN.  Paul.
@EOT:

---