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,e80a1497a689d8a5 X-Google-Attributes: gid103376,public From: "Samuel T. Harris" Subject: Re: Ada and GC (Was Re: Ammo-zilla) Date: 1999/10/30 Message-ID: <381B7AA0.65DDACE5@hso.link.com>#1/1 X-Deja-AN: 542560385 Content-Transfer-Encoding: 7bit References: <38120FAF.945ADD7D@hso.link.com> <7uutgd$87h$1@nnrp1.deja.com> <19991024.18033546@db3.max5.com> <38189268.43EB150F@mail.earthlink.net> <86ogdjtdwz.fsf@ppp-115-70.villette.club-internet.fr> <3818D4F0.92FC4DC9@mail.earthlink.net> <7vc3v5$1888$1@news.gate.net> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii Organization: Raytheon Scientific & Technical Services Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1999-10-30T00:00:00+00:00 List-Id: Vladimir Olensky wrote: > > David Botton wrote in message <7vc3v5$1888$1@news.gate.net>... > >I have found many times that GC can be unacceptable do to unpredictable > >delays even on non-embedded, real-time and safety critical systems. Go > >explain to a power user of large Java programs why they have to > occasionally > >wait to regain usable control of the application do to GC crunching. (I > >believe this had a part in the demise of Corel's Java Office Suite. Applix > >just uses Java like an X terminal and does the real work off site.) > > That's why I wrote that Java GC is not a good "hint" for user controlled GC > and M3 GC is much better in that respect. > > My view is that all objects by default should be UNTRACED. > Only those objects that are subjected to GC should be marked > as TRACED. This approach is opposite to what is done in Modula-3 > but it gives full control to the programmer over GC and it also provides > compatibility with the current Ada 95 implementations > > All the traced objects should be allocated in separate storage pool > controlled > by GC pool storage manager that could provide all needed operations for user > to control GC process. Why not package up this GC as an Ada 95 storage pool and simply associate it to the access types which need GC? With the inclusion of the storage pool concept in Ada 95, I don't see this "to GC or not to GC" within Ada itself as being a _very_ important issue. > > I was pleased very much by the nice Tucker Taft post regarding this > issue. > Now I have a feeling that this issue has grown up and we may expect some > progress in this area soon. > > Regards, > Vladimir Olensky -- Samuel T. Harris, Principal Engineer Raytheon, Scientific and Technical Systems "If you can make it, We can fake it!"