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,e6c9800e35ccfeee X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: GNAT: Performance of String functions Date: 1997/07/22 Message-ID: #1/1 X-Deja-AN: 258207570 References: <5qvdbn$pno$1@ratatosk.uio.no> <5r1l6e$e0h$1@ratatosk.uio.no> Organization: New York University Newsgroups: comp.lang.ada Date: 1997-07-22T00:00:00+00:00 List-Id: iTarjei said <> There is no reason that the implementation has to copy the entire string, it may, but that is an implementation issue, not a language issue. In fact what makes you think you know *anything* about the implementation of bounded string from the RM, it is a private type. You can make the above comment for some particular implementation of Ada, but your statement above, which phrases it as a comment on the language is just plain incorrect. You may be right that if there are aplications that involve a lot of bounded string assignments (I have not seen any yet), and if the implementation does full copies all the time, THEN for that implementation, there may be a problemantic inefficiency. Actually it makes perfectly sense to implement bounded strings in terms of what you call counted strings. That's certainly the implementation plan for GNAT. A side benefit of this approach is that then far less of the implementation is generic.