greenber@utoday.UUCP (Ross M. Greenberg) (05/06/90)
In article <15122@s.ms.uky.edu> sean@ms.uky.edu (Sean Casey) writes: > >Geez is it necessary to have a compiled in 2K static table in every >C file describing the terms of distribution???? > >First we get the GNU people tacking a 3K copyright notice on a 400 byte >program, and now we not only get the same thing on each C file, but >it takes up memory/swap-space to boot! > >How about a notice in each file saying "For conditions of redistribution, >see the COPYING file." > >This is getting ridiculous. Sean, you forgot something. "If you don't like it, don't use it." Or, do you *really* think that you have the right to determine what another person can stick into their code by way of a copyright notice? You don't: it's their code. You are on the other end of the food chain, Sean, as a consumer and not as a producer. -- Ross M. Greenberg, Software Concepts Design, greenber@utoday.UU.NET 594 Third Avenue, New York, New York, 10016 Voice:(212)-889-6431 BIX: greenber MCI: greenber CIS: 72461,3212 BBS:(212)-889-6438
aburt@isis.UUCP (Andrew Burt) (05/07/90)
In article <1696@utoday.UUCP> greenber@.UUCP (Ross M. Greenberg) writes: >"If you don't like it, don't use it." You are on the other end of the >food chain, Sean, as a consumer and not as a producer. In general: Copyrights and other flame war fodder aside, but "the customer is always right" is a prudent attitude to take. In specific: Perhaps an agreeable solution would be to place the LONG copyright notice at the END of the file, with a one line pointer to it at the beginning. (Same for revision histories, etc.) Some of us do read code at 2400 bps or slower, and the copyright doesn't add anything to enjoyment of code (it detracts) and moving it to the end won't fail to prevent any illegal acts that having it at the front would. DEC, Berkeley, etc., are you listening? -- Andrew Burt uunet!isis!aburt or aburt@du.edu "Kwyjibo on the loose!"
john@frog.UUCP (John Woods) (05/10/90)
In article <1696@utoday.UUCP>, greenber@utoday.UUCP (Ross M. Greenberg) writes: > In article <15122@s.ms.uky.edu> sean@ms.uky.edu (Sean Casey) writes: > Or, do you *really* think that you have the right to determine what > another person can stick into their code by way of a copyright notice? Sean did not state or imply that he thought had the right to determine what any other person sticks anywhere. What he implied he had the right to do was to opine that > >This is getting ridiculous. Guess what? He *has* the right to say that. I think he also happens to be correct, but that's immaterial. -- John Woods, Charles River Data Systems, Framingham MA, (508) 626-1101 ...!decvax!frog!john, john@frog.UUCP, ...!mit-eddie!jfw, jfw@eddie.mit.edu