Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!ucbvax!decwrl!sun-barr!texsun!texbell!sequoia!rpp386!jfh
From: jfh@rpp386.Dallas.TX.US (John F. Haugh II)
Newsgroups: comp.unix.xenix
Subject: Re: Problem with C-Kermit for Xenix 2.2.1
Summary: Fix your header files.  And do it soon.
Message-ID: <16891@rpp386.Dallas.TX.US>
Date: 12 Aug 89 03:04:49 GMT
References: <721@kl-cs.UUCP> <8146@spool.cs.wisc.edu>
Reply-To: jfh@rpp386.cactus.org (John F. Haugh II)
Organization: I am NOT the NRA
Lines: 34

In article <8146@spool.cs.wisc.edu> thurm@shorty.cs.wisc.edu (Matthew Thurmaier) writes:
>My experience shows that you need types.h first, then inode.h, then file.h.
>actually, I didn't know of any inter-dependencies between inode and file,
>but I do know that inode.h requires types.h.

The best thing you can do for your sanity is to fix your header files
so they know what their interdependencies are.

If inode.h requires types.h, then you need to have inode.h include
types.h.  The current scam is to have inodes.h include its files and
have each of them insure they aren't seen twice by the compiler.

For example, inodes.h would begin with

#include 

and types.h would begin with

#ifndef _H_TYPES
#define _H_TYPES

...

#endif

If you take the time to add these lines yourself you won't ever
have to worry about them.  And when you finally get that POSIX
and ANSI compliant system we all wish for, you will be ready for
what you see ...
-- 
John F. Haugh II                        +-Quote of the month club: ------------
VoiceNet: (512) 832-8832   Data: -8835  | "Chocolate Teddy Grahams are just
InterNet: jfh@rpp386.cactus.org         |  reincarnated Space Food Sticks."
UUCPNet:  {texbell|bigtex}!rpp386!jfh   +------------     -- Richard Sexton ---