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: otRe: Difference between these pointer syntaxes
Date: Sat, 27 Aug 2016 11:52:17 -0700
Organization: None to speak of
Lines: 25
Message-ID: <lninumdoym.fsf@kst-u.example.com>
References: <nodpg5$cr7$1@dont-email.me> <lnpop7l4bm.fsf@kst-u.example.com> <np2nc9$3h1$1@dont-email.me> <lnwpjfj5ba.fsf@kst-u.example.com> <np4h1p$lq$1@dont-email.me> <kfn4m6hfcnf.fsf@x-alumni2.alumni.caltech.edu> <np81js$jgs$1@dont-email.me> <kfnmvk7ewnu.fsf@x-alumni2.alumni.caltech.edu> <npa81p$iq2$1@dont-email.me> <npp9ao$dno$1@dont-email.me> <nppg0i$4qj$1@dont-email.me> <86fe4ec0-6dcd-4aa0-8a21-f8e57038c3bb@googlegroups.com> <nppmqh$t96$1@jstuckle.eternal-september.org> <npprpa$f7r$1@dont-email.me> <npq0dv$go$1@jstuckle.eternal-september.org> <npq78r$puk$1@dont-email.me> <npq8o9$vdr$1@jstuckle.eternal-september.org> <npqbqh$a4b$1@dont-email.me> <npqn2j$ack$1@jstuckle.eternal-september.org> <npqso8$nag$1@dont-email.me> <nprr18$34g$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="21785"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/t6qVO4dsVugNm8yFzRSEW"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock: sha1:HaQYL6Yuqj/6jZ1KZmxfZe/o+fg= sha1:7PMQWXnXgJ2Vl8LLPHGBFx98ni4=
Xref: csiph.com comp.lang.c:92806

BartC <bc@freeuk.com> writes:
> On 27/08/2016 03:09, Richard Heathfield wrote:
>> On 27/08/16 01:32, Jerry Stuckle wrote:
>>> One correction - any object except a char.
>>
>> It really is high time for you to start backing up such claims. What
>> makes you think the Standard, whether it be C90, C99, or C11, allows you
>> to copy an indeterminate value from a char? Which paragraph, specifically?
>
> I wonder what business it is of a language to stop you reading an 
> indeterminate value if you want?

Nothing stops you from reading an indeterminate value.  The standard
simply doesn't define the behavior of attempting to do so.

Imagine an implementation that marks uninitialized memory and traps
if you attempt to read it.  If reading an indeterminate value were
defined to give you some unspecified value, such an implementation
would be non-conforming.

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