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,9c86eb13dd395066 X-Google-Attributes: gid103376,public From: kilgallen@eisner.decus.org (Larry Kilgallen) Subject: Re: Sequential IO on OpenVMS (was: CRC in Ada?) Date: 1997/03/24 Message-ID: <1997Mar24.151216.1@eisner>#1/1 X-Deja-AN: 228097220 X-Nntp-Posting-Host: eisner.decus.org References: <1997Mar2.220652@nova.wright.edu> <331bf6ce.2832564@news.logica.co.uk> <332B5EBD.3D9E@worldnet.att.net> <332C9185.61C1@worldnet.att.net> <332F5CC8.6D7C@worldnet.att.net> <33320957.B@worldnet.att.net> <3336DC57.25DB@lmtas.lmco.com> X-Nntp-Posting-User: KILGALLEN X-Trace: 859234339/13516 Organization: LJK Software Newsgroups: comp.lang.ada Date: 1997-03-24T00:00:00+00:00 List-Id: In article <3336DC57.25DB@lmtas.lmco.com>, Ken Garlington writes: > By the way, on a related topic: On VAX/OpenVMS systems, the end-of-file > marker > is embedded within the file header. Even for sequential, fixed-length > record files, the EOF can be placed in the middle of a record > (effectively > truncating it). Such a file is certainly an illegal file according to RMS rules. The program which wrote it needs to be fixed. Potentially the system services used by that program need to be fixed by DEC. The possibility of such an illegal file exists, since the various file header bit fields have undefined consequences in certain combinations (and since we are not dealing with the Ada standard I feel free to intermix terms like "undefined", "illegal", "bogus" and "wrong" :-). I certainly believe that it might exist, and for another kind of file which breaks RMS rules, look to VMS executable images. Larry Kilgallen