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=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,1edeadc9be5a2350 X-Google-Attributes: gid103376,public From: nickerson@mirage.vms.boeing.com () Subject: Re: Ada as 2nd Lang, p. 678 Date: 1997/05/09 Message-ID: #1/1 X-Deja-AN: 240352075 Sender: nickerson@mirage.boeing.com () X-Nntp-Posting-Host: pundit.ds.boeing.com References: <5k92el$bs9@ultranews.duc.auburn.edu> Organization: Boeing Defense & Space Group / Software Systems Reply-To: nickerson@mirage.vms.boeing.com () Newsgroups: comp.lang.ada Date: 1997-05-09T00:00:00+00:00 List-Id: In article , dewar@merv.cs.nyu.edu (Robert Dewar) writes: |>The message seems clear enough "file can have only one compilation unit", |>means that a single file can contain only one compilation unit, and the |>file you submitted contains two. The Ada standard says nothing about files, |>or how sources are arranged into files, so this is a place that Ada compilers |>may differ (some Ada compilers do allow multiple units in a single file). |> |>Actually it is generally a bad idea to do what you did -- put the spec and |>the body in the same unit, because that causes an unnecessary connection |>between the two. The whole idea in Ada is to separate the spec and the |>body, so putting them in separate files is recommended in any case. it may "generally" be a bad idea, but "specifically" when one is trying something out or has existing code it is the "reasonable" thing to try; I quite identify with John - myself having used a compiler which did the "expected" thing and allowed multiple units per file; --bn (Bart Nickerson) nickerson@mirage.vms.boeing.com (206) 662-0183