Xref: utzoo rec.games.hack:9273 comp.windows.ms:4231
Path: utzoo!attcan!uunet!mailrus!ncar!boulder!ccncsu!ncuug!seanr
From: seanr@ncuug.UUCP (Sean Reifschneider)
Newsgroups: rec.games.hack,comp.windows.ms
Subject: Re: nethack and mswindows
Message-ID: <14@ncuug.UUCP>
Date: 14 Aug 90 15:17:10 GMT
References: <1990Aug8.070110.245@brolga.cc.uq.oz.au> <1990Aug10.142805.7157@chinet.chi.il.us> <8433@ccncsu.ColoState.EDU> <1990Aug13.152015.1105@chinet.chi.il.us>
Reply-To: seanr@ncuug.UUCP (Sean Reifschneider)
Organization: Northern Colorado Unix Users Group
Lines: 19

In article <1990Aug13.152015.1105@chinet.chi.il.us> patrickd@chinet.chi.il.us (Patrick Deupree) writes:
>In article <8433@ccncsu.ColoState.EDU> mcjilton@handel.UUCP (charles mar mcjilton) writes:
>>I'll be expecting to see the nethack version soon ;-).  It's no small task,
>>I'll warn you.
>
>Being that I've never seen the code, I guess I can't be sure how difficult
>it would be.  Provided it's all in C, however, I should only have to change
>the GUI and possible take care of some addressing issues in some of the
>processing code.  Then again, if the code has anything really wild in it,
>I may have to do some redesign, eh?  @:(

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. 

Sean