Re: seperate keyword and seperate compilation with Gnat?

[smize@Starbase.NeoSoft.COM (Samuel Mize)]

In article <31D95D93.28D8D15B@jinx.sckans.edu>,
David Morton  <dmorton@jinx.sckans.edu> wrote:
>I've been working with John Herro's AdaTutor
>program on Linux, and gnat.
>
>He uses the keyword seperate a lot, to make the assignment 
>procedure in a seperate file, ie,
>
>in file foo.adb  (the test file)
>procedure bar is seperate;
>
>then in file foo-bar.adb
>
>seperate(foo) (the assignment file)
>procedure bar is
>...
>
>He argues that the file foo.adb should be able to be compiled,
>seperately, since the specification is there, even though the actual
>procedure body has not been written.  I'm inclined to believe that he's right,

He's certainly right (at least for Ada83, and I *think* for Ada95)
(unless he's actually spelling it "seperate" in the code).


>but gnat refuses to cleanly compile unless the file foo-bar.adb exists.

The parent unit should compile (but not link).  Might your gnat set-up
be automatically trying to link?  (Just a wild guess.)

Since I haven't seen this mentioned on comp.lang.ada, I assume it
isn't a problem with gnat itself.

Samuel Mize