BIF-C, including source and object files, is licensed under the following 
terms:


------------------------------------LICENSE-------------------------------------

The author or authors grant permission to use and/or redistribute (convey) 
this work in either source or object form under the following terms:


LICENSE:

When redistributing or conveying the code for any purpose, all included 
notices of copyright and/or authorship must be faithfully retained in 
clear and referenceable form.

This license must also be included, as is, neither hidden nor obscured.

Any accompanying files to which other licenses apply shall exlicitly so 
specify in a prominent position within the file.

If this work contains code copied or derived from works assigned to the 
public domain, neither this license nor claims of authorship in this work 
shall be construed to extend to those works. 


DISCLAIMER:

This license SHALL NOT be construed as either endorsement or warranty.

Under this license, THIS SOFTWARE IS PROVIDED AS IT IS, AT NO COST, 
WITHOUT ANY EXPRESS OR IMPLIED WARRANTY OF ANY SORT, INCLUDING, BUT NOT 
LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS OF PURPOSE.

Specifically, under this license, THE AUTHOR OR AUTHORS SHALL NOT BE 
LIABLE FOR ANY DAMAGES WHATSOEVER, DIRECT OR INDIRECT, ARISING FROM THE 
USE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

USE ENTIRELY AT YOUR OWN RISK!


Explanatory notes:

* Use:

Use should be understood to include any reasonable, moral, eithical, 
and legal use. 

This license, of course, does not attempt to deal with illegal use, 
leaving that topic to the applicable laws. 

Moral and ethical use should be considered to be between the user and 
whomever or whatever the user holds to be supreme in such matters.

Reasonable use is left to the user's sense of judgement, with a note 
that the author or authors cannot be held accountable for the user or 
users' lack thereof. 

* Rights of ownership and keeping records: 

It is expected that those who modify either source or object will have 
enough sense to keep records of the original, unmodified form(s), and of 
the modifications they have made. Some sort of source code control is 
recommended. 

At any rate, keeping a copy of the original code used as a starting 
point should help in untangling questions of ownership of code, not to 
mention being invaluable in debugging.

* Public domain work and borrowed code:

At the time of the first release, this work contains significant 
portions of code that are simple translations, in the mathematical sense 
of a regular transformation grammar, from public domain work. Copyright 
on the results of simple translation is very limited, very much dependent 
on the copyrights in the original code. 

While the author(s) claim limited copyright to the resultant translation 
in this case, and full copyright to the use thereof in this work, it 
would be an indefensible display of ingratitude, not to mention unethical, 
to attempt to make claims on the borrowed code itself.

Unfortunately, there are many who seem to assume that they can slap their 
own copyright on public domain work, as children calling out "Dibs! I saw 
it first!" 

For this reason, the license makes special mention of what should be 
obvious about borrowed code in general, that copyright transitivity 
operates in one direction only, and that neither this work nor the 
license thereof can or ought to be used to attempt to reverse that 
transitivity.


--------------------------------END-OF-LICENSE----------------------------------


For the terms of use of BIF 6809, see the files README.TXT and BIFDOC.TXT 
in that distribution.

Much gratitude and appreciation to the forth interest group and the authors 
of the original fig-FORTH models. If you guys want to use any of this stuff 
for something, and the above license is too restrictive, contact me and 
we'll work something out, maybe a special public domain code branch or 
something.

Joel Rees, Reiisi Kenkyuu
