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,ccb8bd6b4c3162fd X-Google-Attributes: gid103376,public From: David Starner Subject: Re: Beginner's questions Date: 1999/05/03 Message-ID: <372E7475.6D884152@aasaa.ofe.org>#1/1 X-Deja-AN: 473777607 Content-Transfer-Encoding: 7bit References: <372da49c.12366381@news.rwth-aachen.de> <372D3B9A.5CBA1ABC@frqnet.de> <372D8919.8CE17514@frqnet.de> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii Organization: Oklahoma State University Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1999-05-03T00:00:00+00:00 List-Id: Andreas Winckler wrote: > > Matthew Heaney wrote: > > > I don't recommend using a heap-based solution (type Unbounded_String) > > unless you have a compelling need to. > > Why? Where's the problem with it? Because high availability is an issue > for me I would be interested in details. I believe he was talking about efficency. Dynamic storage allocations (a superset of heap-based solution) are very inefficent, or at least so my Fortran 77 teacher says. I would recommend checking to see if it's a worry before going out of your way in the name of efficency. I personally have only had one efficency problem, and that ran about 10,000 times too slow due to my mis-estimation of the problem size. YMMV, especially if you're not a student. The only other thing I can think he might have been talking about is that heap-based solutions are hard to use on embedded systems and stuff like that, which might be a worry if you're working on those things.