Re: File Format Compatibility between different compilers

[eachus@linus.mitre.org (Robert I. Eachus)]

In article <313@enstb.enst-bretagne.fr> casado@enstb.enst-bretagne.fr (casado) writes:

> The problems detected were to read meaningless data when the file
> has been created by a program that was compiled by a different compiler.

> Has anybody tried this scenario?

    This is a very good question, but not an easy one to answer. What
an external file looks like is not in the domain of the Ada standard
(there are other ANSI and ISO standards on the subject), and therefore
it is difficult for the RM to mandate a bit layout in an external
file.  Most Ada compiler vendors do a good job of mapping TEXT_IO onto
the standard text file formats for a particular architecture, but when
it come to DIRECT_IO and SEQUENTIAL_IO the situation gets much
messier.

    The easiest thing for a compiler to do is to provide generic IO
packages which copy the internal representations of objects to
external files unchanged.  However different vendors will layout the
same record type differently even on the same hardware, but the bigger
differences are in two different ways to handle discriminated records
and unconstrained array objects.

     Defining a record type EXACTLY with representation clauses is
often enough to make files portable between compilers, but I have had
trouble getting ANSI standard text files from a VAX running VMS to a
VAX running Ultrix, even when using ANSI standard labelled tapes.
--

					Robert I. Eachus

with STANDARD_DISCLAIMER;
use  STANDARD_DISCLAIMER;
function MESSAGE (TEXT: in CLEVER_IDEAS) return BETTER_IDEAS is...