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,7ee10ec601726fbf X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-10-13 00:59:02 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!colt.net!dispose.news.demon.net!news.demon.co.uk!demon!pogner.demon.co.uk!zap!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: why not Date: 13 Oct 2001 08:04:33 +0100 Organization: Pushface Message-ID: References: <3BC30674.BA88AAB6@brighton.ac.uk> <9pvv3t$ves$1@news.huji.ac.il> <7tCx7.26026$ev2.34604@www.newsranger.com> NNTP-Posting-Host: localhost X-NNTP-Posting-Host: pogner.demon.co.uk:158.152.70.98 X-Trace: news.demon.co.uk 1002959935 nnrp-01:5418 NO-IDENT pogner.demon.co.uk:158.152.70.98 X-Complaints-To: abuse@demon.net NNTP-Posting-Date: 13 Oct 2001 07:04:33 GMT X-Newsreader: Gnus v5.7/Emacs 20.7 Xref: archiver1.google.com comp.lang.ada:14451 Date: 2001-10-13T07:04:33+00:00 List-Id: Ted Dennison writes: > I'd say it'd also be nice if there were no "suprise" dynamic > allocations in the unbounded ones either (eg: during lookups). That > would allow for use in situations where heap manipulation is OK > during startup and shutdown, but not during runtime. But getting the > bounded ones clean is more important. If by "lookup" you mean "iteration" then I took your message on board about that as well. Iterators used to use heap allocation with reference counting; now they're all allocated on the stack. This did involve a rather repellent conversion to allow a function to convert the address of a (tagged) container parameter to a pointer-to-writable-container. Down and dirty in the private part. And, if I remember right, one of the problems that stopped the BCs compiling with JGNAT ..