Path: csiph.com!news.swapon.de!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <kst-u@mib.org>
Newsgroups: comp.lang.c
Subject: Re: Difference between these pointer syntaxes
Date: Wed, 17 Aug 2016 18:01:04 -0700
Organization: None to speak of
Lines: 28
Message-ID: <lnk2feki0f.fsf@kst-u.example.com>
References: <nodpg5$cr7$1@dont-email.me> <not07u$k7g$1@dont-email.me> <lna8gdomrv.fsf@kst-u.example.com> <not3oh$nk$1@dont-email.me> <ln60r1ojs3.fsf@kst-u.example.com> <not8so$iji$1@dont-email.me> <ln1t1pog5y.fsf@kst-u.example.com> <notcof$voo$1@dont-email.me> <lnwpjhmy7a.fsf@kst-u.example.com> <notjf6$lqo$1@dont-email.me> <lnshu5msy1.fsf@kst-u.example.com> <notmod$u3t$1@dont-email.me> <lnoa4tmpg1.fsf@kst-u.example.com> <nouo9p$f7o$1@dont-email.me> <lnk2fgn2vv.fsf@kst-u.example.com> <4628cd2d-9333-4be6-943a-eb593c5c4c12@googlegroups.com> <np1pd6$l30$2@dont-email.me> <lnpop7l4bm.fsf@kst-u.example.com> <np2nc9$3h1$1@dont-email.me> <lnwpjfj5ba.fsf@kst-u.example.com> <np2qiv$c73$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: mx02.eternal-september.org; posting-host="945944de09706c9b4e29b53c9d2efdc2"; logging-data="16198"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX192ZMUXbJiiV/I6vflPK/Nz"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock: sha1:n2jBn74GqvYQcXVXu4Zs1sZ64/Q= sha1:nNESmRdpSa29A+tJ2KKVXCb4/1U=
Xref: csiph.com comp.lang.c:92426

BartC <bc@freeuk.com> writes:
> On 18/08/2016 01:20, Keith Thompson wrote:
>> Can you explain what
>>
>>     int arr[10];
>>
>> does in terms of pointers, without references to arrays?  Can you
>> explain the result of `sizeof arr`?
>
> Can you explain why C /didn't/ simply allow arrays to be evaluated? (As 
> Ian suggested.)
>
> What is actually the big deal about dealing with value arrays?
>
> It seems it would have made everything much simpler all round.

I posted some thoughts on that just recently (you may not have seen the
article yet).

But since you refuse to understand how C arrays actually work, I won't
bother discussing with you how they *could* work in some C-like
language.

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"