Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!accuvax.nwu.edu!tank!shamash!odeon!bga
From: bga@odeon.ahse.cdc.com (Bruce Albrecht)
Newsgroups: comp.lang.misc
Subject: Re: Header files
Summary: #include is not really a language construct
Message-ID: <2427@odeon.ahse.cdc.com>
Date: 28 Sep 89 18:38:41 GMT
References: <24955@louie.udel.EDU>
Organization: Control Data Corporation
Lines: 11

In article <24955@louie.udel.EDU>, new@udel.EDU writes:
> One thing I have always liked about the C language was the separation
> between the "header" files (.h) and the "code" files (.c).  ...
> Does anyone know of any relatively popular languages that allow this
> sort of separation other than C and C++?  If not, why not? Discussion?

I will probably have several people tell me I'm wrong about this, but 
#include is a directive for the c pre-processor and not part of the language
itself.  The implication of this, therefore, is that if you have a preprocessor
for your favorite language, you can do this with any language that supports
separately compiled modules.