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:46:38 -0700
Organization: None to speak of
Lines: 17
Message-ID: <ln4lksruup.fsf@kst-u.example.com>
References: <0231327b-9e28-46e4-9178-46c881a8dd91@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> <lnd0zgrvx9.fsf@kst-u.example.com> <554f1564-20b5-4bac-81ed-d603638115ce@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: reader02.eternal-september.org; posting-host="44da38e7affa7c709ac80b82b9bf6f42"; logging-data="16054"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/GLcUFuBoSF6lzIM7AgoLr"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock: sha1:E0FU1EGHbvA9yDCa6jv8mo1CZkc= sha1:LTx0yt+qu50g+5fi6r1ExOXLNwk=
Xref: csiph.com comp.lang.c:128668

supercat@casperkitty.com writes:
[...]
> Note also that it would be possible for a non-interactive implementation
> to react to a stack overflow by cancelling the current execution and
> restarting everything from scratch with a bigger stack, and the behavior
> of such a program would be consistent with how the program would behave
> if the stack didn't overflow.  While such a design would not be practical
> with interactive implementations, such behavior would not be categorically
> impossible.

Only if the program had no side effects prior to the cancellation.

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