Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #128665

Re: Future of C

Path csiph.com!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 Tue, 03 Apr 2018 11:23:30 -0700
Organization None to speak of
Lines 38
Message-ID <lnd0zgrvx9.fsf@kst-u.example.com> (permalink)
References <0231327b-9e28-46e4-9178-46c881a8dd91@googlegroups.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> <9927e2ef-2082-46e2-a1c6-b89da14bae0d@googlegroups.com> <lnpo3hsi3d.fsf@kst-u.example.com> <f387a4d9-496e-4fbe-aca9-7eddc3835292@googlegroups.com>
Mime-Version 1.0
Content-Type text/plain; charset=us-ascii
Injection-Info reader02.eternal-september.org; posting-host="44da38e7affa7c709ac80b82b9bf6f42"; logging-data="5389"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19ALs8Aei1kZjsy0OVHwEiE"
User-Agent Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock sha1:yeqbl/10d2jZvGrf3k7WFQwW90Y= sha1:OKCA75qO42C9NwxXTnu7fPb7IvI=
Xref csiph.com comp.lang.c:128665

Show key headers only | View raw

supercat@casperkitty.com writes:
> On Monday, April 2, 2018 at 11:12:31 AM UTC-5, Keith Thompson wrote:
>> supercat@casperkitty.com writes:
>> [...]
>> > More to the point, while the C Standard seems to have a curious
>> > aversion to doing so, it is possible for it to describe how quality
>> > implementations *should* process a piece of code, without mandating
>> > that all conforming implementations do so.  I would regard stack
>> > overflow in this category, in that there is a clear preferred behavior
>> > [behave in the same fashion as if the stack hadn't overflowed] but
>> > there is nothing a program could do that wouldn't be conforming,
>> > except when running the One Program.
>> 
>> The preferred behavior on stack overflow is to "behave in the same
>> fashion as if the stack hadn't overflowed"?
>> 
>> What??
>
> In most cases where code could hit a translation limit, there Standard
> would define how code should behave if it didn't hit that limit.  The
> Standard may not require that an implementation continue acting as
> defined in the Standard once a translation limit is reached, but that
> doesn't mean that it doesn't define a behavior.

The "preferred behavior" you describe is essentially impossible,
so I'm not sure what your point is.

The standard acknowledges the existence of capacity limits (1p2)
and says that they are outside its scope.  Obviously exceeding a
capacity limit is going to affect a program's behavior in some way.
(Whether that's "undefined behavior" as the standard defines the
term is another matter.)

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

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Re: Future of C Tim Rentsch <txr@alumni.caltech.edu> - 2018-03-26 21:02 -0700
  Re: Future of C David Brown <david.brown@hesbynett.no> - 2018-03-27 09:39 +0200
    Re: Future of C supercat@casperkitty.com - 2018-03-27 07:37 -0700
      Re: Future of C Steven Petruzzellis <frelwizzen@gmail.com> - 2018-03-28 11:19 -0700
  Re: Future of C Steven Petruzzellis <frelwizzen@gmail.com> - 2018-03-27 00:42 -0700
  Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-03-27 08:52 -0700
    Re: Future of C Tim Rentsch <txr@alumni.caltech.edu> - 2018-03-30 07:14 -0700
      Re: Future of C David Brown <david.brown@hesbynett.no> - 2018-03-30 17:23 +0200
        Re: Future of C Steven Petruzzellis <frelwizzen@gmail.com> - 2018-03-31 02:41 -0700
      Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-03-30 09:45 -0700
        Re: Future of C Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-04-02 01:42 -0700
          Re: Future of C Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-02 04:53 -0700
          Re: Future of C supercat@casperkitty.com - 2018-04-02 06:02 -0700
            Re: Future of C Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-02 06:57 -0700
            Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-04-02 09:12 -0700
              Re: Future of C "Chris M. Thomasson" <invalid_chris_thomasson@invalid.invalid> - 2018-04-02 13:30 -0700
                Re: Future of C Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-03 00:59 -0700
              Re: Future of C David Brown <david.brown@hesbynett.no> - 2018-04-02 22:33 +0200
                Re: Future of C Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-04-03 01:40 -0700
                Re: Future of C David Brown <david.brown@hesbynett.no> - 2018-04-03 12:47 +0200
              Re: Future of C supercat@casperkitty.com - 2018-04-03 09:51 -0700
                Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-04-03 11:23 -0700
                Re: Future of C supercat@casperkitty.com - 2018-04-03 11:37 -0700
                Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-04-03 11:46 -0700
                Re: Future of C supercat@casperkitty.com - 2018-04-03 12:26 -0700
                Re: Future of C Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-04-04 01:17 -0700
                Re: Future of C supercat@casperkitty.com - 2018-04-04 09:45 -0700
          Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-04-02 09:10 -0700
            Re: Future of C Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-02 09:33 -0700
            Re: Future of C Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-04-03 01:35 -0700
              Re: Future of C David Brown <david.brown@hesbynett.no> - 2018-04-03 12:50 +0200
                Re: Future of C Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2018-04-03 04:01 -0700
              Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-04-03 09:12 -0700
        Re: Future of C Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-04 16:17 -0700
          Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-04-04 17:26 -0700
            Re: Future of C Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-09 07:30 -0700
              Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-04-09 08:52 -0700
                Re: Future of C Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-11 08:21 -0700
                Re: Future of C Keith Thompson <kst-u@mib.org> - 2018-04-11 09:28 -0700
          Re: Future of C supercat@casperkitty.com - 2018-04-05 11:00 -0700

csiph-web