Path: utzoo!mnetor!uunet!husc6!linus!philabs!pwa-b!mmintl!franka
From: franka@mmintl.UUCP (Frank Adams)
Newsgroups: comp.lang.c
Subject: Re: Teaching const
Message-ID: <2821@mmintl.UUCP>
Date: 18 Apr 88 22:04:48 GMT
References: <7712@apple.Apple.Com> <3034@haddock.ISC.COM> <613@mcrware.UUCP> <7788@alice.UUCP> <27071@amdahl.uts.amdahl.com> <9683@ism780c.UUCP> <786@srs.UUCP> <9719@ism780c.UUCP>
Reply-To: franka@mmintl.UUCP (Frank Adams)
Organization: Ashton-Tate Corporation, East Hartford Development Center
Lines: 17

In article <9719@ism780c.UUCP> marv@ism780.UUCP (Marvin Rubenstein) writes:
>In article <786@srs.UUCP> srs!craig@cs.rochester.edu (Craig Schmackpfeffer) writes:
>>The "int a[1]" declaration ALLOCATES space for an 
>>int and "a" itself is not a pointer.
>But "a" itself a pointer or else *a would not be allowed.

No, "a" itself is an array.  In the context of the "*" operator (and *most*
other contexts) it is *implicitly* converted to a pointer.  The same way in:

int x; long y;
return x+y;

x is implicitly converted to a long.
-- 

Frank Adams                           ihnp4!philabs!pwa-b!mmintl!franka
Ashton-Tate          52 Oakland Ave North         E. Hartford, CT 06108