Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ICAEN.UIOWA.EDU!dbfunk
From: dbfunk@ICAEN.UIOWA.EDU (David B. Funk)
Newsgroups: comp.sys.apollo
Subject: Re: problems compiling pad.h
Message-ID: <8902202054.AA00331@icaen.uiowa.edu>
Date: 20 Feb 89 20:34:56 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: Iowa Computer Aided Engineering Network, University of Iowa
Lines: 31

WRT posting <45056@linus.UUCP>

> When I go to compile
> and include "pad.h" the apollo supplied C compiler barfs
> on the apollo supplied header file - pad.h. This is not
> an encouraging sign.
>   
>   I wrote a test program
> 
>  #include <apollo/pad.h>
>  #include <stdio.h>
> ...

If you read the manual "Programming with Domain/OS Calls" (005506-a00)
you will find out what you are doing wrong. In the middle of page 1-2
there is a paragraph:

 The base insert file, /isr/include/apollo/base.h, declares common data types
 and constants, and calls to manipulate Pascal set data types and should
 generally be included in any prototyped C program that makes Domain/OS
 calls. Thus the preprocessor control lines to include the appropriate insert
 files for a program that makes PAD calls are
 
 #include <apollo/base.h>
 #include <apollo/pad.h>

Almost all <apollo/*.h> include files have the prerequsite of <apollo/base.h>.
I would strengthen the manual's statement and say; always include "base.h" before
any other Apollo specific include files.

Dave Funk