Re: Nested separate compilations

[billwolf@hubcap.clemson.edu (William Thomas Wolfe,2847,)]

From article <4079@hubcap.UUCP>, by wtwolfe@hubcap.UUCP (Bill Wolfe):
> 
>    I have now run into two compilers which balk at nested separate
>    compilations, as per the following example:

   After receiving e-mail to the effect that the ACVC *did* check for this,
   I did some investigation and discovered that the compilers did indeed
   accept the code IF SUBMITTED MANUALLY; it was the automatic recompilation
   facility which was causing the problem.  I had created a directory full
   of foreign code and invoked the automatic compilation-order tool in order
   to get the code compiled, and been rudely informed that the nested
   separate compilation units were missing (utter nonsense) and that c
   compilation was therefore not initiated.  When I collapsed the nested
   separates into the first-level stubs, everything worked perfectly.

   Thanks to everyone who sent mail!  Sorry for the (incorrect) semicolons
   in "separate (whatever);".  This is about the only place where you 
   can't have a semicolon at the end, and every time I make this mistake
   I wonder WHY semicolons are not allowed here, just for consistency reasons..


                                  
                                         Bill Wolfe

                                  wtwolfe@hubcap.clemson.edu