DG> The only references to curses in the online docs was to actual
 DG> cursing at the compiler and it's programs!
 DM>
 DM> (Funny: I actually thought most of the online help was,
 DM> well, helpful, although I wasn't looking for things they
 DM> didn't have, only things they did.)

  It sort of makes you wonder what else is lurking in there
in the venacular.

 DG>   My question was basicly asking if anyone had done up the macros
 DG> or put together a function library for these functions.  Which are
 DG> common for porting from unix.   I didn't want to reinvent the wheel
 DG> again.
 DM>
 DM> Fair enough.  I believe that there have been such ports, although I'm not
 DM> personally aware of any for MSVC, but only for GCC.  Mind
 DM> you, I'm not aware of any for Watcom, either...

    The PD curses have been ported to Watcom and the Borland compilers
 as well, and there are precompiled libraries for them as well.

 DG>     I didn't want to get into the gnu compiler.  Everything there
 DG> is copy lefted, and I'd like to possibly make a little bit of
 DG> money on my other projects.
 DM>
 DM> Common misconception.  The only thing that is copylefted is their code.
 DM> The
 DM> output of their code (i.e., the produced EXE or DLL) is
 DM> *NOT* copylefted, unless it includes copylefted code!  For
 DM> example, the C RTL is *not* copylefted, but the C++
 DM> libraries *are*.  So, if you can compile with gcc without
 DM> include "-lstdc++" or "-lstdcpp" on the linker line, YOUR
 DM> PROGRAM CAN BE SOLD AS COMMERCIAL SOFTWARE.

  I guess it would be possible.  You would just have to write
very carefully.  But that would take all the C++ out of the code.
It would be great for inhouse systems but not for any sort of
marketing.

 DG>     I think that there are a full set of tools in the VC6 package
 DG> (with the latest update from MS).  I am sure that I will be able
 DG> to do the port, it's just going to be a bit more work than I
 DG> anticipated.
 DM>
 DM> Right - you'll need to redo the text output.  Good luck.  :-)

    As shipped the demo example for controling the screen is
 buggie to put it mildly.  You get the opportunity to correct
 hundered of errors (I didn't find out exactly because the
 compiler stopped after 100 errors) which all involved the
 return codes from the functions.  And these bugs were only
 found after you corrected various other bugs in the console.c
 application like forward references to functions and having
 the include file include itself.  The service pack removed
 this particular example... I think.  OR atleast I found a
 working version of it in the CDs with the help of the online
 help.

   I think that I am back on quest again for getting the
chess player out of the modem again.

    Dave

___
 X JABBER v1.2 X A seminar on Time Travel will be held 2 weeks ago

--- Maximus 2.02