Path: utzoo!utgpu!watmath!clyde!att!rutgers!mit-eddie!ll-xn!ames!amdcad!sun!quintus!ok
From: ok@quintus.uucp (Richard A. O'Keefe)
Newsgroups: comp.lang.c
Subject: Re: GROK THIS!!
Keywords: grok
Message-ID: <803@quintus.UUCP>
Date: 3 Dec 88 01:40:08 GMT
References: <1289@leah.Albany.Edu> <3454@ttidca.TTI.COM> <767@quintus.UUCP> <1803@scolex> <14804@mimsy.UUCP>
Sender: news@quintus.UUCP
Reply-To: ok@quintus.UUCP (Richard A. O'Keefe)
Organization: Quintus Computer Systems, Inc.
Lines: 14

In article <14804@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes:
>>In article <767@quintus.UUCP> ok@quintus.UUCP (Richard A. O'Keefe) writes:
>>>To quote the book "'grok' means 'drink'".  (Hence "absorb completely".)

"grok" and the prior use of it by another author were discussed in the
letter column of Analog not too long after Stranger came out.

"grok" is not an appropriate word for Configure to be using, even under
Chris Torek's interpretation.  As some of us found out the hard way, there
are some compilers which accept 'void' but get it wrong in some contexts.
I believe that Configure only requires this weaker "understanding" (it had
*better* be that way, otherwise people using old broken compilers are
likely to give the wrong answer), so a more accurate phrase would be
"does your compiler _accept_ 'void'".