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.8 required=5.0 tests=BAYES_00,PLING_QUERY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,c9c0b66bbaefa4f2 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-08-17 03:57:13 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: dewar@gnat.com (Robert Dewar) Newsgroups: comp.lang.ada Subject: Re: best way to handle long strings!? Date: 17 Aug 2002 03:57:13 -0700 Organization: http://groups.google.com/ Message-ID: <5ee5b646.0208170257.7418c149@posting.google.com> References: NNTP-Posting-Host: 205.232.38.14 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1029581833 16480 127.0.0.1 (17 Aug 2002 10:57:13 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 17 Aug 2002 10:57:13 GMT Xref: archiver1.google.com comp.lang.ada:28163 Date: 2002-08-17T10:57:13+00:00 List-Id: jonas.gasser@dataflow.ch (drmed) wrote in message news:... > hi, > > for example: for a texteditor or sourceditor is it usefull to use the > unbounded strings? and to put all lines in one string? or is there a > better method to handle this? Putting all the data in one long unbounded string is a perfectly frightful choice. Almost anything else would be better.