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: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!border2.nntp.dca1.giganews.com!buffer2.nntp.dca1.giganews.com!border2.nntp.dca3.giganews.com!backlog4.nntp.dca3.giganews.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.earthlink.com!news.earthlink.com.POSTED!not-for-mail NNTP-Posting-Date: Fri, 18 Jul 2014 07:41:17 -0500 From: Dennis Lee Bieber Newsgroups: comp.lang.ada Subject: Re: Mission-Critical Design: Ada.Unchecked_Deallocation vs Garbage Collection Date: Fri, 18 Jul 2014 08:41:21 -0400 Organization: IISS Elusive Unicorn Message-ID: <755is9pqec24if5ecnatvc05uindaphd40@4ax.com> References: X-Newsreader: Forte Agent 6.00/32.1186 X-No-Archive: YES MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Usenet-Provider: http://www.giganews.com NNTP-Posting-Host: 76.249.29.160 X-Trace: sv3-FuStod6wv8Gqp1/EqpHYBYCL4QuQoU9DdKsDEvOzA7UdMFPRvubmYi54D1UAdLvpdpwpgObB7gefbG2!ggdskovA/ljlZD9vULBmHGUA0Yk/ApeUqXEr9xIgvSqhWtxBxROPRHsxBzVA86oEEh25I1ZdDVCp!ybNRcGn7BN7X7j8lsuHgUJ1qQc4= X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 X-Original-Bytes: 2097 Xref: news.eternal-september.org comp.lang.ada:21044 Date: 2014-07-18T08:41:21-04:00 List-Id: On Thu, 17 Jul 2014 23:17:48 -0700 (PDT), NiGHTS declaimed the following: >In mission-critical design applications, do they favor garbage collectors or the unchecked deallocation? > Based upon the examples I've seen at work (flight management systems): NEITHER... Any dynamic memory gets allocated during the initialization step (based on some configuration "file" to identify how much of each component to create), and once that completes the only "dynamic" memory is the stack (and not even the secondary stack used in some operations -- like run-time string concatenation; no: put("string " & integer'image(val) & " more"); ) -- Wulfraed Dennis Lee Bieber AF6VN wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/