Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!ptsfa!ihnp4!homxb!mtuxo!rolls!doug!tim
From: tim@doug.UUCP (Tim J Ihde)
Newsgroups: comp.lang.c
Subject: Re: $include
Message-ID: <360@doug.UUCP>
Date: Tue, 1-Dec-87 10:17:56 EST
Article-I.D.: doug.360
Posted: Tue Dec  1 10:17:56 1987
Date-Received: Sun, 6-Dec-87 07:58:26 EST
References: <10528@brl-adm.ARPA>
Sender: news@doug.UUCP
Organization: AT&T ISL - Somerset, NJ
Lines: 23
Summary: Sounds like a database program

In article <10528@brl-adm.ARPA>, PAWKA@NOSC-TECR.arpa writes:
> 	While looking through some source for a SUN 3/160 running BSD 4.2, I
> found the following:
> 
> $include 
> 
> What's with the "$include", we have quite a few of these sprinkled throughout?


Some of the more popular database packages use $include in order to insure
sufficient confusion.  Both Informix ESQL and Unify use them.  At least
in the case of Unify, there is no real reason why a #include could not be
used; it seems to me that ESQL has a more valid excuse but its been awhile
since I've used it and I don't remember.  You should be able to tell what
is happening, becuase whatever is processing the $'s must be doing it in
a precompile phase, before cpp kicks in.  Usually you will find that the
Makefile is redefining CC to another program that processes the $includes
and then calls cc (for Unify, you use "CC=ucc").

In any case, I've noticed that the $'s really confuse programs such as
lint or nmake.  Ah well . . .

	tim