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,cc4f25d878383cc X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-12-03 16:26:00 PST Path: archiver1.google.com!news1.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!newsfeed1.earthlink.net!newsfeed.earthlink.net!newsmaster1.prod.itd.earthlink.net!newsread1.prod.itd.earthlink.net.POSTED!not-for-mail Message-ID: <3C0C0A34.EE726EA5@earthlink.net> From: "Marc A. Criley" Organization: Quadrus Corporation X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Another Idea for Ada 20XX References: <3C0AACCE.329CFB60@worldnet.att.net> <3C0B65CB.8CDD7B31@earthlink.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 04 Dec 2001 00:25:57 GMT NNTP-Posting-Host: 158.252.122.153 X-Complaints-To: abuse@earthlink.net X-Trace: newsread1.prod.itd.earthlink.net 1007425557 158.252.122.153 (Mon, 03 Dec 2001 16:25:57 PST) NNTP-Posting-Date: Mon, 03 Dec 2001 16:25:57 PST X-Received-Date: Mon, 03 Dec 2001 16:25:59 PST (newsmaster1.prod.itd.earthlink.net) Xref: archiver1.google.com comp.lang.ada:17366 Date: 2001-12-04T00:25:57+00:00 List-Id: Larry Kilgallen wrote: > > In article <3C0B65CB.8CDD7B31@earthlink.net>, "Marc A. Criley" writes: > > > The problem was that one program wrote a file of floating point numbers > > representing values in British units, which was then read by a program > > that expected floating point numbers representing metric units. No unit > > information accompanied the values in the file, they were just numbers. > > Do space probes include file systems and multiple programs ? > > Or is this something in the build environment ? > > If the latter, the problem could be solved by an old fashioned EDP > tool called a data dictionary. The error occurred in the ground-based navigational processing, not onboard the spacecraft. And oh yes, there are many ways to avoid such a problem--any of the assorted manifestations of interface control documents, for instance.