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.6 required=5.0 tests=BAYES_05,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!attcan!uunet!lll-winken!ames!pasteur!ucbvax!skvax1.csc.ti.com!linnig
From: linnig@skvax1.csc.ti.com
Newsgroups: comp.lang.ada
Subject: trouble with separate();
Message-ID: <8901131806.AA19832@ti.com>
Date: 13 Jan 89 17:48:13 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
List-Id: <comp.lang.ada>

>    I have now run into two compilers which balk at nested separate
>    compilations, as per the following example:
>       procedure A is
>          procedure B is separate;
>       begin [...] end A;
>       ------------ in another file... ---------------
>       separate (A);    <-- error here??
>       procedure B is
>          procedure C is separate;
>       begin [...] end B;

If you are submiting these examples to your compiler I'd be
surprised if it didn't balk:  

You should not have a semicolon after "SEPARATE(A)"	

This is something I usually forget too. Once I removed the extra semicolons
and changed the elipsis to "NULL;" your example program compiled without
error (under Tartan Ada). I agree... your compiler should be able to handle
such nestings.

	Mike Linnig,
	Texas Instruments