Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!uunet!mcvax!kth!sunic!dkuug!tidk!storm
From: storm@texas.dk (Kim F. Storm)
Newsgroups: comp.sources.d
Subject: Re: nn and 80286 processors
Keywords: patches
Message-ID: <354@texas.dk>
Date: 5 Jul 89 16:45:22 GMT
References: <803@cimcor.mn.org> <1415@garcon.cso.uiuc.edu>
Organization: Texas Instruments, Denmark
Lines: 18

In article <1415@garcon.cso.uiuc.edu> mcdaniel@uicsrd.csrd.uiuc.edu (Tim McDaniel) writes:

>0,1,0 is indeed incorrect; the compiler has to know that the 0s are
>pointers and not just ints (since null pointers are permitted to have
>a size and/or internal representation different than an int 0).

I fully agree, but I was fooled by the following wording in the
curses manual:  "The simplest call would be setupterm(0,1,0) which
uses all the defaults", so that is what I did.

I have included the various patches for the '286 in patch #4 which
is scheduled for friday this week, and have fixed quite a few additional
16/32 bit inconsistencies.  I don't have access the a '286 myself, but
at least none of the patches can do any harm, and they may even work :-)
-- 
Kim F. Storm        storm@texas.dk        Tel +45 429 174 00
Texas Instruments, Marielundvej 46E, DK-2730 Herlev, Denmark
	  No news is good news, but nn is better!