Xref: utzoo rec.games.hack:9313 comp.windows.ms:4297
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!uunet!microsoft!t-jlee
From: t-jlee@microsoft.UUCP (Johnny LEE)
Newsgroups: rec.games.hack,comp.windows.ms
Subject: Re: nethack and mswindows
Message-ID: <56635@microsoft.UUCP>
Date: 16 Aug 90 18:42:05 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> <14@ncuug.UUCP>
Reply-To: t-jlee@microsoft.UUCP (Johnny LEE)
Organization: Microsoft Corp., Redmond WA
Lines: 39

In article <14@ncuug.UUCP> seanr@ncuug.UUCP (Sean Reifschneider) writes:
>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

I'd expect that he'd have to change very little of the core Nethack
code in order to make it work under Windows. The Mac port handles
events very nicely and you'll find very few references to
the Mac event-handling code in the core Nethack code. It supports
the mouse, menus, colour, and a custom font for display purposes.
Most of this is hidden in the code for inputting a character.

An MS Windows version is going to need more than 640K of memory,
easily. The overlay team went thru ulcer-inducing contortions
to make Nethack fit in under 640K.

All I can say is good luck. :-)


Johnny Lee
t-jlee@microsoft.UUCP
...!uunet!microsoft!t-jlee
For one more month: Standard Disclaimer