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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,386228a37afe967f X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-07-21 08:46:30 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!feed2.news.rcn.net!rcn!nntp.abs.net!ash.uu.net!spool.news.uu.net!not-for-mail Date: Mon, 21 Jul 2003 11:46:29 -0400 From: Hyman Rosen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030611 Thunderbird/0.1a X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Computer Language Shootout References: <1ec946d1.0307150715.4ba69f85@posting.google.com> <3F149243.80304@attbi.com> <3F15930C.2070907@attbi.com> <87k7aeqfcf.fsf@inf.enst.fr> <3F19E1BB.5000908@attbi.com> <87n0f9poyc.fsf@inf.enst.fr> <3F1A98F4.3090304@attbi.com> <87r84lt987.fsf@inf.enst.fr> <3F1B1AE9.8040409@attbi.com> <87el0kth5w.fsf@inf.enst.fr> <1058798392.73480@master.nyc.kbcfp.com> <87k7abj43f.fsf@inf.enst.fr> In-Reply-To: <87k7abj43f.fsf@inf.enst.fr> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Organization: KBC Financial Products Message-ID: <1058802389.227844@master.nyc.kbcfp.com> Cache-Post-Path: master.nyc.kbcfp.com!unknown@nightcrawler.nyc.kbcfp.com X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/) NNTP-Posting-Host: 204.253.250.10 X-Trace: 1058802389 2095 204.253.250.10 Xref: archiver1.google.com comp.lang.ada:40560 Date: 2003-07-21T11:46:29-04:00 List-Id: Samuel Tardieu wrote: > But I still think that in a vast majority of cases, it is a good thing > that users ask themselves "what is the biggest line length I will ever > get?" and write such a function only if they really need to. No, it is a terrible thing. To this day, I cannot open up a large xterm on my Sun workstation and run "vi". It tells me "Screen too large for internal buffer". UNIX utilities used to be full of such line limits until the GNU folks came along and eliminated them from their versions of the programs. Many of the old utilities would silently truncate long lines, or consider them to be multiple lines, or crash. I have had the experience of needing to run text utilities on an ordinary text file which happened to have lines which were several hundred thousand characters long. No utility author would ever have specified such a large limit.