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=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,147f221051e5a63d X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Path: g2news1.google.com!postnews.google.com!j22g2000hsf.googlegroups.com!not-for-mail From: Matthew Heaney Newsgroups: comp.lang.ada Subject: Re: memory management in Ada: tedious without GC? Date: Mon, 19 May 2008 08:37:11 -0700 (PDT) Organization: http://groups.google.com Message-ID: References: <4ddef8bf-b5b1-4d7e-b75b-386cd6c8402c@l17g2000pri.googlegroups.com> <482E8A9D.5040401@obry.net> <8640a12f-da99-435f-8eb6-372e175cd5b9@z72g2000hsb.googlegroups.com> <482F19CE.7060306@obry.net> <87d4nkzhtn.fsf@willow.rfc1149.net> <2545491.n7xu0MFufK@linux1.krischik.com> <5209773.UsCT0IWhbo@linux1.krischik.com> <82e2924a-4888-4b45-a4de-f33f905334c2@n1g2000prb.googlegroups.com> <155a4acc-8898-4316-88df-0b161bdadd9a@c58g2000hsc.googlegroups.com> <5f570e87-fd87-48cb-b991-a76c30648e79@y38g2000hsy.googlegroups.com> NNTP-Posting-Host: 66.162.65.129 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1211211432 32703 127.0.0.1 (19 May 2008 15:37:12 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Mon, 19 May 2008 15:37:12 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: j22g2000hsf.googlegroups.com; posting-host=66.162.65.129; posting-account=umyUbgkAAADe5rQC4VzV-ffCoH4N30u3 User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727),gzip(gfe),gzip(gfe) Xref: g2news1.google.com comp.lang.ada:244 Date: 2008-05-19T08:37:11-07:00 List-Id: On May 19, 4:39=A0am, Maciej Sobczak wrote: > > I've found two differences: > 1. No support for exception-safe assignment in Ada. It depends on how you define "exception-safe". Assignment in Ada makes only a "basic guarantee" wrt exception safety; that is, state is not preserved but invariants are preserved. (State is not preserved because finalization of the LHS happens before the assignment proper.) Here's a helpful article that defines "basic" vs. "strong" vs. "no- throw" guarantees: http://www.boost.org/community/exception_safety.html > 2. Memory leak after exception is raised while initializing the > allocated object in Ada. If by "initializing" you mean invoking a controlled action (Initialize), then you'd get Propgram_Error, which means you have a broken program anyway. I do forget the exact rules about memory reclaimation, though; if I do this: declare P : T_Access :=3D new T; begin and the initialization of the object designed by P fails (e.g. because controlled initialization fails, which raises Program_Error, or because component initialization fails, which raises Constraint_Error), then what does the language say about reclaiming the memory allocated for P.all? Good question...