Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!linac!att!ucbvax!dog.ee.lbl.gov!elf.ee.lbl.gov!torek
From: torek@elf.ee.lbl.gov (Chris Torek)
Newsgroups: comp.unix.programmer
Subject: Re: Nice() in Sys V.4
Keywords: nice(), priocntl(), ioctl()
Message-ID: <11393@dog.ee.lbl.gov>
Date: 24 Mar 91 02:08:49 GMT
References: <previous> <posting> <318@secola.Columbia.NCR.COM> <1991Mar21.141753.28726@nncrcae.Columbia.NCR.COM>
Reply-To: torek@elf.ee.lbl.gov (Chris Torek)
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 19
X-Local-Date: Sat, 23 Mar 91 18:08:49 PST

In article <1991Mar21.141753.28726@nncrcae.Columbia.NCR.COM>
wescott@Columbia.NCR.COM (Mike Wescott) writes:
[quoting proc(4) from some SVR4 system]
>	The argument p is a generic pointer whose  type  depends  on
>	the  specific  ioctl code.  Where not specifically mentioned
>	below, its value should be  zero.

Whoop!  Whoop!  Confusion alert!

Does this mean `the argument p should be a null-pointer-to-char', or
does it mean `the argument p should be a pointer-to-char holding the
address of an int whose value is zero', or does it mean something else?

It is impossible for p to have the `value ... zero' because p is a
pointer---Pointers Are Not Integers---but this means we must guess at
what was really meant.
-- 
In-Real-Life: Chris Torek, Lawrence Berkeley Lab CSE/EE (+1 415 486 5427)
Berkeley, CA		Domain:	torek@ee.lbl.gov