Re: inclusion of header files lead to derived works

[Henning Makholm <henning@makholm.net>]

Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de> writes:

> I think this is flawed. A header file consists of

> * function names,
> * function arguments,
> * macro definition,
> * inline code,
> * type declarations

> Furthermore, those are the realization of a concept, which constitutes a
> copyrightable amount of work.

With the exception of nontrivial macro definitions and inline
functions (which do not appear in "mainstream" header files for C)
what the header file contains is irrelevant, because it does not
appear (neither verbatim NOR translated) in the binary.

In fact, a header file is primarily used for typechecking, which is a
task that is completed at compile time. There is no type information
in object code.

-- 
Henning Makholm