Path: csiph.com!news.swapon.de!eternal-september.org!feeder.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <kst-u@mib.org>
Newsgroups: comp.lang.c
Subject: Re: Future of C
Date: Mon, 02 Apr 2018 09:10:57 -0700
Organization: None to speak of
Lines: 24
Message-ID: <lntvstsi5q.fsf@kst-u.example.com>
References: <0231327b-9e28-46e4-9178-46c881a8dd91@googlegroups.com> <20180311000302.8e7cd15242a818ab75eb2e98@gmail.com> <83527acf-abed-4f8f-878c-7d4db9cd5ac1@googlegroups.com> <c7g9add2d3mgc6ksk4c4f4500ivubjuog9@4ax.com> <20180311161525.ac591de531b83d6b14b2cd43@gmail.com> <90236828-48d7-4ee5-9b86-4cedd0e29b5f@googlegroups.com> <hwhpC.902622$F74.120435@fx47.am4> <d9d91c28-fb38-400b-8b92-ce7ce7d2b9cd@googlegroups.com> <3r7jne-t3h.ln1@gangtai.grep.be> <8e201938-ada4-42d9-8ae6-13b1047306e2@googlegroups.com> <lnina0c1xg.fsf@kst-u.example.com> <JrEpC.185321$mN7.7780@fx16.am4> <69a08d82-b76a-4334-be63-20dc22f869bf@googlegroups.com> <lna7vcbw69.fsf@kst-u.example.com> <0dcf08ee-d589-444c-8122-5310d95e80df@googlegroups.com> <p88srs$17c$1@dont-email.me> <kfna7uunp2c.fsf@x-alumni2.alumni.caltech.edu> <ln7epxwm5h.fsf@kst-u.example.com> <kfnh8oxlkfn.fsf@x-alumni2.alumni.caltech.edu> <lnin9dtsuo.fsf@kst-u.example.com> <d96f52ff-e2dd-40b8-b260-31359f5417e5@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: reader02.eternal-september.org; posting-host="59c91fcd0d5933af9c9624494db21dc4"; logging-data="13531"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+CWYj+7LgujYRs+tRC6N4f"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock: sha1:gbAvWlTa8+jVSM60XcxUxzKafrI= sha1:ssQPCjUWnRh7dnZWcot/TWkZh4Q=
Xref: csiph.com comp.lang.c:128641

Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:
[...]
> Something can be undefined in C standard terms if the C standard
> says that it is undefined. It is undefined in normal parlance if the 
> C standard does not provide a definition for the behaviour. Stack
> overflow is obviously in the latter category. 

Are you ignoring N1570 4p2?

    If a "shall" or "shall not" requirement that appears outside
    of a constraint or runtime-constraint is violated, the behavior
    is undefined. Undefined behavior is otherwise indicated in this
    International Standard by the words "undefined behavior" or by
    the omission of any explicit definition of behavior. There is 
    no difference in emphasis among these three; they all describe
    "behavior that is undefined".

I already cited it in this thread.

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