Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!seismo!mcvax!ukc!eagle!icdoc!cam-cl!am
From: am@cam-cl.UUCP
Newsgroups: comp.lang.c
Subject: Re: Distinguished pointers (was Re: Weird syscall returns)
Message-ID: <1045@jenny.cl.cam.ac.uk>
Date: Mon, 17-Aug-87 10:37:47 EDT
Article-I.D.: jenny.1045
Posted: Mon Aug 17 10:37:47 1987
Date-Received: Sat, 22-Aug-87 09:05:36 EDT
References: <1158@copper.TEK.COM> <8317@utzoo.UUCP> <854@mcgill-vision.UUCP>
Reply-To: am@cl.cam.ac.uk (Alan Mycroft)
Organization: U of Cambridge Comp Lab, UK
Lines: 16

In article <854@mcgill-vision.UUCP> mouse@mcgill-vision.UUCP (der Mouse) writes:
>> 	char myio_no;
>> 	char myio_null;
>> And then include this in the include file for your library:
>> 	#define	NOFILE		((FILE *)&myio_no)
>> 	#define	NULLFILE	((FILE *)&myio_null)
>
>Hm.  I see no guarantee that NOFILE != NULLFILE.  Do it right:
>
>FILE myio_no;
>FILE myio_null;
>#define NOFILE (&myio_no)
>#define NULLFILE (&myio_null)
>
Hm.  I see no guarantee that FILE is not a function type, which invalidates
your suggestion.  :-)