Xref: utzoo rec.games.hack:9327 comp.windows.ms:4342
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mcdchg!chinet!patrickd
From: patrickd@chinet.chi.il.us (Patrick Deupree)
Newsgroups: rec.games.hack,comp.windows.ms
Subject: Re: nethack and mswindows
Message-ID: <1990Aug17.221709.20330@chinet.chi.il.us>
Date: 17 Aug 90 22:17:09 GMT
References: <8433@ccncsu.ColoState.EDU> <1990Aug13.152015.1105@chinet.chi.il.us> <14@ncuug.UUCP>
Organization: The Whitewater Group, Evanston, IL
Lines: 26

In article <14@ncuug.UUCP> seanr@ncuug.UUCP (Sean Reifschneider) writes:
>You would have to redesign the code completely for MS Windows.  The way that
>you write programs is completely opposite of most systems (because Windows
>has to call your program when you get a message, and you have to return
>from that function when you're done, otherwise, windows won't multitask).
>Try picking up a book on MS Windows, and check out how you have to do the
>work. 

Actually, I won't have to redesign the code completely.  I was hoping that my
theory was correct and I wasn't disappointed.  See, Hack is designed for
use in different computers.  This being the case, the I/O seems to have been
modularized (e.g. separated) from the rest of the program.  Basically I'll
only have to change the way this I/O works.  The other good thing is
that it seems this works for a MAC so it is definatly modularized to
the point where I/O is separate.

I've got most all of the code downloaded so I should have a chance to work on
this over the weekend.  Oh, and I've been programming Windows and
supporting it for about a year and a half now.  While this doesn't make me an
expert, I am still well aware of the tricks of the trade and have read a
few books on this.
-- 
"Organized fandom is composed of a bunch of nitpickers with a thing for
 trivial pursuit."  -Harlan Ellison

Patrick Deupree ->	patrickd@chinet.chi.il.us