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,6c43f45c2ab47c51 X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!news1.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!wns14feed!worldnet.att.net!attbi_s21.POSTED!53ab2750!not-for-mail From: "Jeffrey R. Carter" User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Using Ada.Containers.Vector and Limited Private types References: <8ff4c6c2-9892-463e-bdfd-1f7bfd78d607@s50g2000hsb.googlegroups.com> <4c5bfeb0-daa0-45e4-82f0-eebabda565e9@d45g2000hsc.googlegroups.com> <6QQdk.194211$TT4.37376@attbi_s22> <940db060-ef08-4e1c-9556-0514181183eb@j22g2000hsf.googlegroups.com> <%BWdk.194588$TT4.100135@attbi_s22> <16cdae3f-83fa-4bd2-a9d1-3750518ff9d8@y38g2000hsy.googlegroups.com> In-Reply-To: <16cdae3f-83fa-4bd2-a9d1-3750518ff9d8@y38g2000hsy.googlegroups.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <4yrek.251407$yE1.227224@attbi_s21> NNTP-Posting-Host: 12.201.97.213 X-Complaints-To: abuse@mchsi.com X-Trace: attbi_s21 1215972608 12.201.97.213 (Sun, 13 Jul 2008 18:10:08 GMT) NNTP-Posting-Date: Sun, 13 Jul 2008 18:10:08 GMT Organization: AT&T ASP.att.net Date: Sun, 13 Jul 2008 18:10:08 GMT Xref: g2news1.google.com comp.lang.ada:1137 Date: 2008-07-13T18:10:08+00:00 List-Id: Gene wrote: > > You might want to be careful about this. I guess it depends how soft > soft is. Internally it looks like GNAT ends up calling gcc malloc/free > for UBS. Implementations of malloc/free can have wildly varying > performance depending on current heap structure. Your app may meet > time requirements today on test data and fail tomorrow because the > heap has fragmented in a different way. We are aware of the potential problems with Unbounded_String, but so far we are in actual use without problems. Since Unbounded_String is, conceptually at least, just a controlled wrapper around a pointer to String, we would expect to have to deal with the same problems if we manipulated such pointers directly. If we do encounter problems, we will probably replace Unbounded_String with some sort of bounded string. -- Jeff Carter "What lazy lout left these wires all over the lawn?" Poppy 98