Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!crdgw1!camelback!volpe
From: volpe@camelback.crd.ge.com (Christopher R Volpe)
Newsgroups: comp.lang.c
Subject: Re: Is typedef char BUFFER[20] legal?
Message-ID: <16562@crdgw1.crd.ge.com>
Date: 8 Feb 91 13:18:57 GMT
References: <1212@tredysvr.Tredydev.Unisys.COM> <1991Jan29.210100.8105@zoo.toronto.edu> <22642@netcom.UUCP> <23128@netcom.COM>
Sender: news@crdgw1.crd.ge.com
Reply-To: volpe@camelback.crd.ge.com (Christopher R Volpe)
Lines: 15

In article <23128@netcom.COM>, avery@netcom.COM (Avery Colter) writes:
|>(Array names are not strictly objects, right? Like a pointer, a direct
|> reference to it yields an address value, but unlike a pointer the
|> array name's value itself cannot be changed.)

Actually, array names do in fact refer to objects, that is, they are
unmodifiable lvalues. In most contexts, a reference to it is
converted to an address value (i.e. pointer to first element), but this 
doesn't occur if it is the operand of '&' or 'sizeof' or the
left operand of '='.
                                                                
==================
Chris Volpe
G.E. Corporate R&D
volpecr@crd.ge.com