Is there a difference between a "module" and a "compilation unit" ?

[Bob]

Are they different names for the same concept ?

 

[Chris Torek]

Are they different names for the same concept ?

[For clarity about the pronoun "they", I will repeat the subject
line for those whose news-delivery systems mangle it:]

Is there a difference between a "module" and a "compilation unit" ?

That depends on who does the defining, no?

The C standards define the term "translation unit". They do not
define either "compilation unit" or "module". Thus, this newsgroup
(comp.lang.c) cannot give you a definitive answer to the question.

In languages that actually have modules (such as Modula-2 and
Modula-3), I might claim there is a subtle difference, in that
a module may require more than one compilation step and each
such step could be termed a "unit". But you would have to define
these terms with respect to C before you could get an answer.

 

[Bob]

That depends on who does the defining, no?
Yes.

The C standards define the term "translation unit". They do not
define either "compilation unit" or "module". Thus, this newsgroup
(comp.lang.c) cannot give you a definitive answer to the question.

So be it: "translation unit" will be used (by me) from now on.

Thanks.

 

[pete]

So be it: "translation unit" will be used (by me) from now on.

A translation unit is the output of the preprocessor.
A translation unit consists of a sequence of external declarations.

 

[Peter Nilsson]

pete wrote:
-> Bob wrote:
-> > > > Is there a difference between a "module" and a
-> > > > "compilation unit" ?
-> > >
-> > > That depends on who does the defining, no?
-> >
-> > Yes.
-> >
-> > > The C standards define the term "translation unit". They do
-> > > not define either "compilation unit" or "module". Thus, this
-> > > newsgroup (comp.lang.c) cannot give you a definitive answer
-> > > to the question.
-> >
-> > So be it: "translation unit" will be used (by me) from now on.
->
-> A translation unit is the output of the preprocessor.
-> A translation unit consists of a sequence of external declarations.

Section 5 says... "An implementation translates C source files..."

"Source file" probably makes more sense than translation unit, or
preprocessing translation unit (which by definition may consist of
more than one file.)

Although programming has the concept of modules, C generally doesn't.
There is no immediate way to share objects with external linkage
exclusively within a select group of source files.

 

[Bob]

Although programming has the concept of modules, C generally doesn't.
There is no immediate way to share objects with external linkage
exclusively within a select group of source files.

Exactly. Something like what Delphi does for example, if I'm not
mistaken.