Newsgroups: comp.lang.c
Path: utzoo!henry
From: henry@utzoo.uucp (Henry Spencer)
Subject: Re: const, volatile, etc [was Re: #defines with parameters]
Message-ID: <1988Dec13.172510.16345@utzoo.uucp>
Organization: U of Toronto Zoology
References: <674@quintus.UUCP> <117@halcdc.UUCP> <468@auspex.UUCP> <9016@smoke.BRL.MIL> <10919@ulysses.homer.nj.att.com> <1450@micomvax.UUCP> <369@aber-cs.UUCP>
Date: Tue, 13 Dec 88 17:25:10 GMT

In article <369@aber-cs.UUCP> pcg@cs.aber.ac.uk (Piercarlo Grandi) writes:
>... In Classic C the concept was that the compiler would
>take register as an hint of which variables could always be safely cached in
>register (and the user be forbidden to take pointer to them), and all the
>others could be cached only if it was guaranteed that doing so would not
>"cause surprises".

Please cite references for this.  It's never been true.
-- 
SunOSish, adj:  requiring      |     Henry Spencer at U of Toronto Zoology
32-bit bug numbers.            | uunet!attcan!utzoo!henry henry@zoo.toronto.edu