🚀 go-pugleaf

In article <314ED5A2.2CF7@ccm.fm.intel.com>, "Aaron C. Coday"
<aaron_coday@ccm.fm.intel.com> writes
>Has anyone out there ported signficant amount of code from Solaris
>to Windows NT?  If so, I would like to hear about it.  Particularly
>any pitfalls, etc.
>
>I'm facing possibly porting a large project to Windows NT.  As I 
>understand it, it should be easier than trying to port to
>Windows 3.x, because Solaris and NT both use flat memory models.

In my "day job" I work on and maintain the NT version of a large
distributed application development toolkit which runs on a dozen
different varieties of Unix, as well as NT, OS/2, VMS etc. I did the
original port from Unix to NT of this product.

It really is pretty easy; Unix code written with portability in mind (as
our code is) ports pretty much straight off to NT. For networking, NT's
socket library is virtually the same as the standard Unix Berkeley
sockets library, and almost all Unix system calls have 1:1 equivalents
in NT.

You really shouldn't have too many problems.

Chris

--------------------------------------------------------------------------
 Chris Marriott, Warrington, UK      | Author of SkyMap v3 award-winning 
 chris@chrism.demon.co.uk            | shareware Win31/Win95 planetarium.
            For full info, see http://www.execpc.com/~skymap  
      Author member of Association of Shareware Professionals (ASP) 
--------------------------------------------------------------------------