Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sunybcs!bingvaxu!cjoslyn
From: cjoslyn@bingvaxu.cc.binghamton.edu (Cliff Joslyn)
Newsgroups: comp.lang.c
Subject: Re: chronic source of confusion in C
Keywords: arrays in C
Message-ID: <3019@bingvaxu.cc.binghamton.edu>
Date: 16 Feb 90 04:52:22 GMT
References: <1486@mdbs.UUCP> <22550@mimsy.umd.edu>
Reply-To: cjoslyn@bingvaxu.cc.binghamton.edu.cc.binghamton.edu (Cliff Joslyn)
Organization: SUNY Binghamton, NY
Lines: 21

In article <22550@mimsy.umd.edu> chris@mimsy.umd.edu (Chris Torek) writes:
>As for the lattermost question: I suspect that yes, many people who
>teach C do not understand how C arrays work---that is, do not understand
>that C arrays are, at best, second class citizens; that there are no
>array values, only array objects.

This posting comes at a very opportune time for me: I am a new C
teacher, and I begin arrays (not pointers yet) next week, with much
trepidation.  Chris, I have read your postings with much interest, but
am sure I don't have your Complete Story of Arrays and Pointers.  If
this is a good time to repost something like that (complete yet
concise), I would be greatly appreciative, and the net might welcome it
as well.  Perhaps you have something prepared to post.  Or, email would
be welcome. 

Thanks.
-- 
O------------------------------------------------------------------------->
| Cliff Joslyn, Cybernetician at Large, cjoslyn@bingvaxu.cc.binghamton.edu
| Systems Science, SUNY Binghamton, Box 1070, Binghamton NY 13901, USA
V All the world is biscuit shaped. . .