Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.lang.c
Subject: Re: include files -- help needed
Message-ID: <13897.Jun2723.11.3691@kramden.acf.nyu.edu>
Date: 27 Jun 91 23:11:36 GMT
References: <1991Jun26.091408.5023@thunder.mcrcim.mcgill.edu> <1991Jun26.213114.236@druid.uucp> <4896@inews.intel.com>
Organization: IR
Lines: 24

In article <4896@inews.intel.com> bhoughto@bishop.intel.com (Blair P. Houghton) writes:
> In article <1991Jun26.213114.236@druid.uucp> darcy@druid.uucp (D'Arcy J.M. Cain) writes:
> >Why go through that?  I assume you mean that you have something like time.h
> >and sys/time.h so just prepend _SYS_ to the defines in the sys directory:
> Anyone know a system where one's not just a {link,symlink} to the other?

Yep: a perfectly-standard-except-all-those-little-porting-bugs BSD 4.3
system.

> What is the difference?

They're not just different. They're incompatible. They end up defining
struct tm in two different ways; the people who ported the system to
this hardware managed to copy the definition from somewhere else to
<sys/time.h>.

As another example, our BSD 4.3+NFS Mt. XINU system has struct tm in
<time.h>. <sys/time.h> has various timefoo definitions for various foo,
then #ifndef KERNEL #include <time.h> #endif.

In any case, there are lots of other examples of include files where you
want to prepend the directory name instead of assuming a flat namespace.

---Dan