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,5997b4b7b514f689
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Reading a line of arbitrary length
Date: 1997/03/06
Message-ID: <dewar.857651560@merv>#1/1
X-Deja-AN: 223528444
References: <5ds40o$rpo@fg70.rz.uni-karlsruhe.de> <1997Mar3.082830.1@eisner>
 <JSA.97Mar3141341@alexandria> <dewar.857447653@merv>
 <5fh5g0$80h@fg70.rz.uni-karlsruhe.de>
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1997-03-06T00:00:00+00:00
List-Id: <comp.lang.ada>


Thomas said

<<In a realtime application, I do not want to have time-critical parts
interrupted by GC.>>

Well certainly not, but obviously garbage collectoin needs to be under
programmer control at least to the extent of turning it on or off, presumably
by using the storage pool mechanism, or options having the same effect.
I do not think that is what we are talking about here in discussing
GC API's.