| eli.bendersky | 4afc9f2 | 2011-09-24 06:27:33 +0300 | [diff] [blame^] | 1 | The authors of this software are Christopher W. Fraser and
|
| 2 | David R. Hanson.
|
| 3 |
|
| 4 | Copyright (c) 1991,1992,1993,1994,1995,1996,1997,1998,1999,2000,2001,2002
|
| 5 | by AT&T, Christopher W. Fraser, and David R. Hanson. All Rights Reserved.
|
| 6 |
|
| 7 | Permission to use, copy, modify, and distribute this software for any
|
| 8 | purpose, subject to the provisions described below, without fee is
|
| 9 | hereby granted, provided that this entire notice is included in all
|
| 10 | copies of any software that is or includes a copy or modification of
|
| 11 | this software and in all copies of the supporting documentation for
|
| 12 | such software.
|
| 13 |
|
| 14 | THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED
|
| 15 | WARRANTY. IN PARTICULAR, NEITHER THE AUTHORS NOR AT&T MAKE ANY
|
| 16 | REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY
|
| 17 | OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE.
|
| 18 |
|
| 19 |
|
| 20 | lcc is not public-domain software, shareware, and it is not protected
|
| 21 | by a `copyleft' agreement, like the code from the Free Software
|
| 22 | Foundation.
|
| 23 |
|
| 24 | lcc is available free for your personal research and instructional use
|
| 25 | under the `fair use' provisions of the copyright law. You may, however,
|
| 26 | redistribute lcc in whole or in part provided you acknowledge its
|
| 27 | source and include this CPYRIGHT file. You may, for example, include
|
| 28 | the distribution in a CDROM of free software, provided you charge only
|
| 29 | for the media, or mirror the distribution files at your site.
|
| 30 |
|
| 31 | You may not sell lcc or any product derived from it in which it is a
|
| 32 | significant part of the value of the product. Using the lcc front end
|
| 33 | to build a C syntax checker is an example of this kind of product.
|
| 34 |
|
| 35 | You may use parts of lcc in products as long as you charge for only
|
| 36 | those components that are entirely your own and you acknowledge the use
|
| 37 | of lcc clearly in all product documentation and distribution media. You
|
| 38 | must state clearly that your product uses or is based on parts of lcc
|
| 39 | and that lcc is available free of charge. You must also request that
|
| 40 | bug reports on your product be reported to you. Using the lcc front
|
| 41 | end to build a C compiler for the Motorola 88000 chip and charging for
|
| 42 | and distributing only the 88000 code generator is an example of this
|
| 43 | kind of product.
|
| 44 |
|
| 45 | Using parts of lcc in other products is more problematic. For example,
|
| 46 | using parts of lcc in a C++ compiler could save substantial time and
|
| 47 | effort and therefore contribute significantly to the profitability of
|
| 48 | the product. This kind of use, or any use where others stand to make a
|
| 49 | profit from what is primarily our work, requires a license agreement
|
| 50 | with Addison-Wesley. Per-copy and unlimited use licenses are
|
| 51 | available; for more information, contact
|
| 52 |
|
| 53 | Mike Hendrickson
|
| 54 | Addison Wesley Professional
|
| 55 | 75 Arlington St.
|
| 56 | Boston, MA 02116
|
| 57 | 617/848-6522 FAX: 617/848-6569 mikeh@awl.com
|
| 58 |
|
| 59 | -----
|
| 60 | Chris Fraser / cwfraser@microsoft.com
|
| 61 | David Hanson / drh@microsoft.com
|
| 62 | $Revision: 1.8 $ $Date: 2002/08/27 00:02:26 $
|