From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.1 required=5.0 tests=BAYES_05,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,faf964ea4531e6af X-Google-Attributes: gid103376,public X-Google-Thread: 1025b4,43ae7f61992b3213 X-Google-Attributes: gid1025b4,public From: Barry Margolin Subject: Re: GPL and "free" software Date: 1999/05/04 Message-ID: #1/1 X-Deja-AN: 474004119 Distribution: world References: <7fibd5$jc7$1@news2.tor.accglobal.net> <372F2C65.4B7663C5@doc.ic.ac.uk> <372F36AB.55833EA6@doc.ic.ac.uk> X-Abuse-Info: Otherwise we will be unable to process your complaint properly X-Complaints-To: abuse@gte.net X-Trace: +LPib6W2jhtgFMWO80xFpVQyAUx8OSWj9KtZ9hrxtuGx05bAou+aXHAn8QOApmMelA0PD/3WoSMq!guzwbFMrWbTRPcVIWl5tdgY3mT1dHXNKemzc0vyjIPRvKYlvDJF/Y0fYZrMTAQ== Organization: GTE Internetworking, Cambridge, MA X-Copies-To: never NNTP-Posting-Date: Tue, 04 May 1999 18:25:50 GMT Newsgroups: comp.lang.ada,gnu.misc.discuss Originator: barmar@bbnplanet.com (Barry Margolin) Date: 1999-05-04T00:00:00+00:00 List-Id: In article <372F36AB.55833EA6@doc.ic.ac.uk>, Ed Avis wrote: >Barry Margolin wrote: > >>>I meant that something like: >>> >>>#define BUFFER_SIZE 1000 >>>#define MAX_THINGIES 6 >>> >>>probably isn't copyrightable, especially once you strip away the names >>>and are just left with the pair of integers '1000, 6'. > >>It certainly is copyrightable. The choice of names is a significant part >>of programming. A header file that says: >> >>#define ASDFASDF 1000 >>#define LKJLKJLK 6 >> >>is quite different from the above file. > >My point was, the only part of the header file which gets included in >the final executable (or, indeed, in the .S file) is the two numbers >1000 and 6. So my header file and yours would give identical object >code. I don't see how the number six can be copyrighted, except >perhaps in relation to the Children's Television Workshop. Suppose you have a program that contains: #include ... printf ("%d, %d\n", BUFFER_SIZE, MAX_THINGIES); If you compile this file, you'll get a different object file depending on whether somefile.h contains: #define BUFFER_SIZE 1000 #define MAX_THINGIES 6 or #define BUFFER_SIZE 6 #define MAX_THINGIES 1000 Thus, the object file is derived from the header file. >I thought that very small snippets of code were not copyrighted. They are, but in some cases copying small snippets out of a larger work might be fair use, and hence not infringing. There are a number of criteria that must be satisfied for a copy to be fair use, and size in proportion to the entire work is just one of them. Perhaps a court might decide that the way that header files are typically used constitutes fair use. AFAIK, it's never been tested. Years ago I worked for a company that produced an operating system and compilers. It was quite common for programmers at the time to produce compiler listings that included all the header files inserted. IIRC, we took the copyright notices *out* of our header files so that these listing files wouldn't appear to be copyrighted by the vendor. Our PL/I compiler didn't support macros, so the only stuff in the header files were function prototypes and structure declarations, and we weren't concerned about them being copied. -- Barry Margolin, barmar@bbnplanet.com GTE Internetworking, Powered by BBN, Burlington, MA *** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups. Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.