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,4b862d91ff93feff X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Text_IO for other standard types Date: 1998/01/14 Message-ID: #1/1 X-Deja-AN: 316060333 References: <98010912585349@psavax.pwfl.com> <34BA9133.7B4B@online.no> <69cfdt$3q$1@peuplier.wanadoo.fr> <69hr3i$sd5$1@goanna.cs.rmit.edu.au> <34BD2DCF.2A29@online.no> X-Complaints-To: usenet@news.nyu.edu X-Trace: news.nyu.edu 884833368 445 (None) 128.122.140.58 Organization: New York University Newsgroups: comp.lang.ada Date: 1998-01-14T00:00:00+00:00 List-Id: Tarjei said The page/line stuff is not exactly nonsense, but a very strange priority of allocating resources. It is almost exclusively useful for generating reports. It's about as useful as the bit_order attribute - if my interpretation of 13.5.3 matches reality. Your interpretation may be wrong, this attribute is quite useful Isn't it usually the I/O time that is dominant in situations like this? BTW. I have yet to inspect the actual code. Not at all, it is much more likely that such an application is CPU bound (one that does formatted IO)