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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,f6f130eea077b8f8 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-05-27 13:18:08 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!sn-xit-03!sn-xit-01!sn-post-02!sn-post-01!supernews.com!corp.supernews.com!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: AI-248 and counting the elements in an external file Date: Tue, 27 May 2003 15:19:10 -0500 Organization: Posted via Supernews, http://www.supernews.com Message-ID: References: <$YW1v+vxIWob@eisner.encompasserve.org> <3ECFEB59.4010401@attbi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Newsreader: Microsoft Outlook Express 4.72.3612.1700 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3719.2500 X-Complaints-To: abuse@supernews.com Xref: archiver1.google.com comp.lang.ada:37860 Date: 2003-05-27T15:19:10-05:00 List-Id: Larry Kilgallen wrote in message ... >In article <3ECFEB59.4010401@attbi.com>, "Robert I. Eachus" writes: >> Larry Kilgallen wrote: >> >>> Meaning it is permissible to return the number of 512-byte disk blocks >>> (or file-specific-size tape blocks) for this function on VMS ? Or is the >>> answer supposed to be normalized to bytes even though the number of >>> overhead bytes required (and thus the file size) will vary, for instance, >>> when copying a file from disk to tape ? >> >> Let me answer differently. VMS supports many file formats. Ada stream >> files would map nicely to VMS record oriented ANSI tape files. There >> are other VMS formats that I would not tend to support stream files for. > >But my understanding is that the Ada.Directory functions are to support >all files that might be accessed from Ada, and that is not limited to >stream files, nor to files written by Ada. The intent is that it be well-defined (which might include raising Use_Error if if cannot be figured out, as for a keyboard) for files that can be read or written by Ada. If Ada doesn't understand the files at all, then we're not trying to say anything. I would expect that this functionality would take more work on some OSes than it does on Windows or Unix. On the original CP/M, for instance, you had to figure out the file size by finding out the block size and multiplying it by the number of blocks. That's fine, and keep in mind that this result really is intended to report the physical size of the file, which may or may not be directly relatable to the 'logical' size returned by Direct_IO.Size and Stream_IO.Size. Randy.