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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,29850945228df59 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-06-17 10:37:52 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!arclight.uoregon.edu!wn13feed!wn12feed!worldnet.att.net!4.24.21.153!chcgil2-snh1.gtei.net!news.bbnplanet.com!chcgil2-snf1.gtei.net!news.gtei.net!news.binc.net!kilgallen From: Kilgallen@SpamCop.net (Larry Kilgallen) Newsgroups: comp.lang.ada Subject: Re: Boehm-Demers-Weiser conservative garbage collector and GNAT Date: 17 Jun 2003 12:37:49 -0500 Organization: Berbee Information Networks Corporation Message-ID: References: <1316747.mXveBPtf0Z@linux1.krischik.com> In article , Ludovic Brenta writes: > Kilgallen@SpamCop.net (Larry Kilgallen) writes: > >> The last major program I wrote was designed to minimize the amount >> of explicit memory allocation (using Ada83). There were one or two >> chains of records that had to be cleaned up in between major groups >> of user commands. >> >> There was a "lot" of stack-based memory used. > > Interesting. Did you encounter special difficulties designing your > program with this particular goal in mind? Like for example > limitations on the size of the stack, or problems sharing objects > between threads? This was not a multi-threaded application, and the primary stack size is limited only by a general operating system quota that also affects heap size Heap + Stack < Limit