Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!bionet!ames!hc!lanl!cmcl2!phri!cooper!dasys1!jpr
From: jpr@dasys1.UUCP (Jean-Pierre Radley)
Newsgroups: comp.sources.d
Subject: Re: nn and 80286 processors
Message-ID: <10180@dasys1.UUCP>
Date: 11 Jul 89 05:05:23 GMT
References: <803@cimcor.mn.org> <1415@garcon.cso.uiuc.edu>
Reply-To: jpr@dasys1.UUCP (Jean-Pierre Radley)
Organization: TANGENT
Lines: 20

In article <1415@garcon.cso.uiuc.edu> mcdaniel@uicsrd.csrd.uiuc.edu (Tim McDaniel) writes:
>In article <803@cimcor.mn.org> mike@cimcor.mn.org (Michael Grenier)
>writes (more or less):
>> Changed arguments in call to setupterm to NULL,1,NULL from 0,1,0 in term.c...
>0,1,0 is indeed incorrect
>Therefore, to change 0,1,0 to NULL,1,NULL will ... be incorrect as before.
>The correct fix is to cast NULL to the proper argument type, as in
>        (struct foobar *) NULL, 1, (struct stoat *) NULL


The file already contains a #define NONE,
which is NULL cast to a character pointer.

So, on my 386 box, I found that I should
replace
	0,1,0
by
	NONE,1,NONE
-- 
Jean-Pierre Radley		CIS: 72160,1341		jpr@jpradley.UUCP