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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,d1df6bc3799debed
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Syntax for tagged record types (was Re: Not intended for use in
 medical,)
Date: 1997/05/25
Message-ID: <dewar.864589478@merv>#1/1
X-Deja-AN: 243871079
References: <3.0.32.19970423164855.00746db8@mail.4dcomm.com>
 <33828299.2A3@world.std.com> <mheaney-ya023680002005972314260001@news.ni.net
 <mheaney-ya023680002105972302430001@news.ni.net> <EALJpp.HnH@world.std.com>
 <33850721.49BF@sprintmail.com>
 <mheaney-ya023680002305970103110001@news.ni.net>
 <JSA.97May23142418@alexandria>
 <mheaney-ya023680002305972133010001@news.ni.net>
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1997-05-25T00:00:00+00:00
List-Id: <comp.lang.ada>


Matthew says

<<Safety-critical applications won't use the heap, so let's try to build a
more expressive language for use on those kinds of applications.  Eliminate
the requirement for heap - by adding features (such as constructors) for
applicative programming using limited types - and you eliminate the need
for a garbage collector.>>

That's an over-generalization. Many safety critical programming protocols
allow the use of the heap for allocation only at initialization time. 
Otherwise you end up with quite unnecessary restrictions that do not add
to safety, e.g. you lose the possibility of parametrizing sizes of variable
length objects.