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,145c4a0f1a1fc553 X-Google-Attributes: gid103376,public From: "Marin David Condic, 561.796.8997, M/S 731-96" Subject: Re: Resonable to assume format Stream_IO = Direct_IO? Date: 1997/10/03 Message-ID: <97100309420454@psavax.pwfl.com>#1/1 X-Deja-AN: 277610114 Sender: Ada programming language Comments: To: dale@goanna.cs.rmit.edu.au X-VMS-To: SMTP%"INFO-ADA@VM1.NODAK.EDU" X-VMS-Cc: SMTP%"dale@GOANNA.CS.RMIT.EDU.AU",CONDIC Newsgroups: comp.lang.ada Date: 1997-10-03T00:00:00+00:00 List-Id: Dale Stanbrough writes: > >I know that Dec's Ada83 compiler put all sorts of extra things into >a direct_io file; is this implementation freedom still taken advantage >of by Ada95 vendors? > My experience with VMS files is that they store all sorts of stuff in files (and their headers) besides the data. VMS imposed structure on a file beyond just a file name and a bag of bytes. This is true even for text files. This is why it is very difficult to duplicate the "COPY" DCL command since there's so much hidden information that's carried along with the file. So VMS would be a bad example. (More an OS issue than a compiler implementation issue.) Unix tends to treat all files as a simple stream of bytes, so I'd expect the stream_io stuff might work in most cases as you'd expect. But so much of this seems like it will depend on if the OS provides some sort of specialized file structure. I could imagine, for example, that if an OS provided some kind of ISAM file, direct_io might map on top of that rather easily, but stream_io wouldn't be able to look at it without getting lots of garbage data. Is the platform you're looking at a Unix environment? MDC