From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 border1.nntp.dca3.giganews.com!backlog3.nntp.dca3.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newspeer1.nac.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: Heartbleed
Date: Sat, 12 Apr 2014 19:39:11 +0100
Organization: A noiseless patient Spider
Message-ID: <lymwfqo0j4.fsf@pushface.org>
References: <1ljwj8f.1wqbhvuabsdw1N%csampson@inetworld.net>
 <51c7d6d4-e3be-44d5-a4ce-f7e875345588@googlegroups.com>
 <li9g34$9q8$1@dont-email.me> <%J32v.70539$kp1.45343@fx14.iad>
 <liap70$ckq$1@speranza.aioe.org>
 <87mwfq4vvj.fsf@kuiper.lan.informatimago.com>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx05.eternal-september.org;
 posting-host="a0d4eb314a073b71869f2de305ad0700";
 logging-data="28225"; mail-complaints-to="abuse@eternal-september.org";
 posting-account="U2FsdGVkX19q80hrCTy6fcxfYtGLRfJwMVUj1pgyff4="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (darwin)
Cancel-Lock: sha1:T95PRhgWxepl5wnkSdvPXHZQW04=
 sha1:SB7PGG+BwF154MkT9vnnPGGDeQ4=
X-Original-Bytes: 1883
Xref: number.nntp.dca.giganews.com comp.lang.ada:185709
Date: 2014-04-12T19:39:11+01:00
List-Id: <comp.lang.ada>

"Pascal J. Bourguignon" <pjb@informatimago.com> writes:

> But strongly late dynamically typed programming languages are probably
> better for mission critical systems, since they can adapt dynamically
> the type of the values at run-time, instead of crashing.

If the system designers have thought about what to do under such
circumstances so that the system can carry on, OK,

If not, the system is operating outside its design envelope, which I
think is equivalent to the Ada "erroneous behaviour; so you don't know
_what_ it will do, and the best response is probably to fall back to a
pre-planned recovery mode. Or, as you say, to crash; which has at least
the virtue, during development, of making it obvious that there's a
problem to be fixed.