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=0.1 required=5.0 tests=BAYES_05,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,c70f02b79bc3d231
X-Google-Attributes: gid103376,public
From: mfb@mbunix.mitre.org (Michael F Brenner)
Subject: Re: dynamic memory allocation
Date: 1997/06/17
Message-ID: <5o6oij$55b@top.mitre.org>#1/1
X-Deja-AN: 249131981
References: <33A55F1B.63FE@gsfc.nasa.gov> <dewar.866539898@merv>
 <33A6A38D.658B@gsfc.nasa.gov>
Organization: The MITRE Corporation, Bedford Mass.
Newsgroups: comp.lang.ada
Summary: Rigorous research on truly-hard-real-time system allocation is rare
Date: 1997-06-17T00:00:00+00:00
List-Id: <comp.lang.ada>


To: Stephen.Leake@gsfc.nasa.gov
Subject: Re: dynamic memory allocation

Some discussion on very conservative memory allocation (either no
dynamic memory allocation or allocation only at the beginning
and then no de-allocation) can be seen at:

   The OberonT Language
   Hard Real-Time Systems
   Cache Coherency

Unfortunately, there is very little reasearch done (outside of NASA,
MITRE, and the rest of the hard-real-time community) to rigorously
prove ways to make something last many years. They just dont need it.
Consumers accept text editors, operating systems, Net browsers,
spread sheets, command and control systems, e-mail software,
airplane avionics, fragmented disks, traffic lights, billing systems,
government services, databases, year 2000 problems, and teller
machines that Hang the Mouse (that is, run off the end of a
hanging pointer or sieze due to memory fragmentation). For example,
most managers of messaging systems suffering from Year 2000 overflows have
no intention of changing the messages from 2-digit
to 4-digit years, because they feel they can afford the consequences.

Mike mikeb@mitre.org