Path: csiph.com!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: extern array as a pointer
Date: Tue, 12 Jul 2016 11:30:39 -0700
Organization: None to speak of
Lines: 25
Message-ID: <lntwfuhfow.fsf@kst-u.example.com>
References: <27db6ff2-216f-41c6-a9e0-c06d206f5262@googlegroups.com> <nm2ho6$455$1@dont-email.me> <20160712135839.349cd1a4@archvm> <lnbn22izsv.fsf@kst-u.example.com> <nm377p$k9q$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="10262"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19R6aKydRuJVwcM6GcjX9MJ"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock: sha1:3aO5C+CDPimt9zRMCc83xUdrTY0= sha1:8hU1kGycqDDVbLJz7OD+algKPtg=
Xref: csiph.com comp.lang.c:90297

James Kuyper <jameskuyper@verizon.net> writes:
> On 07/12/2016 12:30 PM, Keith Thompson wrote:
>> Frank Tetzel <s1445051@mail.zih.tu-dresden.de> writes:
>> [...]
>>> But why? Why is "extern int *array" containing the first element which
>>> is 0? Why doesn't the compiler or rather the linker warn about this? Is
>>> the type information lost for the linker?
>> 
>> Yes, that's exactly the problem: the linker is required to pay attention
>> to type information.
>
> Is there a "not" missing from that sentence?

OOPS!

Yes, what I meant was:

Yes, that's exactly the problem: the linker is not required to pay
attention to type information.

-- 
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"