Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/3/84; site wjh12.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!wjh12!kendall
From: kendall@wjh12.UUCP (Sam Kendall)
Newsgroups: net.lang.c
Subject: K&R and lvalues (Re: Re: limitations of casts, ...)
Message-ID: <536@wjh12.UUCP>
Date: Tue, 30-Oct-84 17:22:46 EST
Article-I.D.: wjh12.536
Posted: Tue Oct 30 17:22:46 1984
Date-Received: Wed, 31-Oct-84 06:32:10 EST
References: <120@harvard.ARPA> <5487@brl-tgr.ARPA> <122@harvard.ARPA> <5505@brl-tgr.ARPA>
Organization: Delft Consulting Corp., New York
Lines: 12

> > K&R 'defines' an lvalue as an 'expression referring to an object'.
> > and an object as a 'manipulable region of storage'. '(char *)x' is a
> > perfectly good lvalue: it refers to the object 'x' considered as
> > a pointer to a character.
> 
> K&R is not at all clear about lvalues.  That shows why we need a good
> standards document.

K&R is pretty clear about this one: it is not an lvalue.

	Sam Kendall	  {allegra,ihnp4,ima,amd}!wjh12!kendall
	Delft Consulting Corp.	    decvax!genrad!wjh12!kendall