Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!rutgers!sri-spam!ames!ucbcad!ucbvax!hplabs!hp-pcd!uoregon!koblas From: koblas@uoregon.UUCP (David Koblas) Newsgroups: comp.lang.c Subject: Re: $include Message-ID: <1153@uoregon.UUCP> Date: Sat, 28-Nov-87 15:39:43 EST Article-I.D.: uoregon.1153 Posted: Sat Nov 28 15:39:43 1987 Date-Received: Tue, 1-Dec-87 03:52:21 EST References: <10528@brl-adm.ARPA> <275@westmark.UUCP> Reply-To: koblas@drizzle.UUCP (David Koblas) Organization: University of Oregon, Computer Science, Eugene OR Lines: 27 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] #include ... ] . ] . ] . ] #include ] $include ] ] What's with the "$include", we have quite a few of these sprinkled throughout? One posibility is that the program was written using the UNIFY database, since they have their own set of 'compilers' (really shell scripts, that finally invoke the real thing). If they are $including "file.h" this is a good indication of what this is otherwise it would be hard to tell. Also if it is using functions like 'inscrf', 'acckey', 'ptube', 'pfield', 'makeset', this would be another good indication. -- _______________________________________________________________________________ Name: David Koblas Place: University of Oregon Chemstores Path: ...!tektronix!uoregon!koblas Domain: koblas@uoregon.{bitnet,UUCP,csnet}