/* $XConsortium: copyright.h,v 1.6 91/04/16 15:03:32 rws Exp $ */
/*
Copyright 1991 by the Massachusetts Institute of Technology
Permission to use, copy, modify, distribute, and sell this software and its
documentation for any purpose is hereby granted without fee, provided that
the above copyright notice appear in all copies and that both that
copyright notice and this permission notice appear in supporting
documentation, and that the name of M.I.T. not be used in advertising or
publicity pertaining to distribution of the software without specific,
written prior permission. M.I.T. makes no representations about the
suitability of this software for any purpose. It is provided "as is"
without express or implied warranty.
*/
This, obviously, looks nothing like the give-it-away COPYING file(s) in the
Guile src tree. So, what's it going to be?
Some questions...
1) If I write object modules that extend Guile and are loaded dynamically, am
I required to provide the source code for these modules if I sell them?
2) How about if I compile a Guile command-line interpreter and link my modules
in statically, am I required to provide the source for these modules?
3) If instead of a command-line program, I wish to build the interpreter into
a parent application (eg. an X window app with a command line of its own
or a program that uses a file written in scheme as a setup file), am I
required to provide the source for the parent program?
In all of the above cases, I wish to _sell_ the resulting executable ( #1 is a
little different, in that I want to sell the .o files ).
Anyone have a definitive answer for this with supporting documentation?
Thanks.
-Tom
----------------------------------------------------------------------------
Tom McKay PO Box 13665
Senior Software Engineer Research Triangle Park, NC 27713
Integrated Silicon Systems, Inc. 919.941.6628
mckay@isscad.com Fax: 919.941.6700
----------------------------------------------------------------------------