8 April 2019\r
\r
\r
- BIF documentation Copyright Joel Matthew Rees 1992, 2019\r
+BIF documentation Copyright 1992, 2000, 2019 Joel Matthew Rees\r
+BIF source and object Copyright 1992, 2000, 2019 Joel Matthew Rees\r
+https://ja.osdn.net/projects/bif-6809/\r
\r
\r
In the spirit of fig-FORTH, the author grants permission as follows:\r
ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS \r
SOFTWARE.\r
=========\r
+(This is essentially the ISC license.)\r
\r
If the copyright notices in this file and the README.TXT file are \r
retained, including that file and this with your distribution will\r
BIF is architecturally derived from fig-FORTH. fig-FORTH comes courtesy\r
of the FORTH INTEREST GROUP, PO Box 1105, San Carlos, CA 94070.\r
\r
-The author also grants permission to use and copy the source and object\r
-code for BIF freely, with the same stipulations, i. e.,\r
-that any distribution of significant portions of either must be\r
-accompanied by this notice, and the additional stipulation that any\r
-distribution of the entire code, whether source, object, or both, must\r
-be accompanied by the entire documentation, including Copyright and\r
-acknowledgements.\r
-\r
This is not a commercial product; it was a student project, use it at\r
your own risk. No warranty whatsoever is made concerning it. (If, by\r
chance, anyone is interested in using BIF in a commercial product, I\r
DISKS FORMATTED FOR USE BY OTHER OPERATING SYSTEMS WHILE BIF IS RUNNING!\r
\r
Contact as of January 2000:\r
- joel_rees@sannet.ne.jp\r
- http://www.page.sannet.ne.jp/joel_rees\r
- reiisi@nettaxi.com\r
- http://www.nettaxi.com/citizens/reiisi\r
+ http://reiisi.blogspot.com\r
+ joel.rees+knock@gmail.com\r
+ https://defining-computers.blogspot.com/\r
+ https://ja.osdn.net/users/reiisi/\r
+ https://sourceforge.net/u/reiisi/profile/\r
+ \r
\r
\r
*******************************************************************************\r
Information about BIF as of April 2019.\r
\r
- Joel Rees, Amagasaki, Hyogo, Japan.\r
- joel.rees@gmail.com\r
+ Joel Matthew Rees, Amagasaki, Hyogo, Japan.\r
+ https://ja.osdn.net/projects/bif-6809/\r
+ joel.rees+knock@gmail.com\r
http://reiisi.blogspot.com\r
https://defining-computers.blogspot.com/\r
+ https://ja.osdn.net/users/reiisi/\r
+ https://sourceforge.net/u/reiisi/profile/\r
etc.\r
- \r
+ Copyright 2000, 2019 Joel Matthew Rees\r
+\r
-----\r
\r
(The following can be found in its original form in the bif-c \r
the Color Computer 3, with the expected limitations of requiring the \r
32 column screen, etc. \r
\r
-License information -- the rights to BIF and restrictions on \r
-distribution -- are described in the file BIFDOC.TXT, which really \r
-should distributed with the source.\r
+License information -- the rights to BIF and the materials with it, \r
+and restrictions on distribution -- are described in the file \r
+BIFDOC.TXT, which really should distributed with the source along with \r
+this README.TXT. \r
+\r
+The short version of the licensing information is that I am distributing \r
+BIF6809 under the essential terms of the Internet Systems Consortium \r
+ISC License:\r
+\r
+=========\r
+Permission to use, copy, modify, and/or distribute this software for \r
+any purpose with or without fee is hereby granted, provided that the \r
+accompanying copyright notices and this permission notice appear in \r
+all copies.\r
+\r
+THE SOFTWARE IS PROVIDED “AS IS” AND ISC DISCLAIMS ALL WARRANTIES \r
+WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF \r
+MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY \r
+SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES \r
+WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN \r
+AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, \r
+ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS \r
+SOFTWARE.\r
+=========\r
\r
I add here the stipulation that I claim right to the word "BIF" as \r
the name of a programming language.\r
\r
If you are going to distribute or redistribute the obect or source of \r
bif in any of its forms, it really makes no sense not to include the \r
-BIFDOC.TXT. If you do something like that and you or anyone that gets \r
-the results has problems with it, and you come to me looking for help, \r
-expect to be teased mercilessly about it. And expect to be on the \r
-bottom of my priority list (not out of spite, out of self-protection).\r
+BIFDOC.TXT and this README.TXT. If you do something like that and \r
+you or anyone that gets the results has problems with it, and you come \r
+to me looking for help, expect to be teased mercilessly about it. And \r
+expect to be on the bottom of my priority list, not out of spite, \r
+out of self-protection.\r
\r
-----\r
\r
and a post-fix assembler.\r
PAIRS.G28, PAIRS.G28.out\r
a "database" example from one of my FORTH books.\r
+TOOLS_G00_ERRORS.text\r
+ Contains the tools output readable in regular text editor format \r
+ and the error messages, with their corresponding number in \r
+ hexadecimal. I should make a separate file for the error messages\r
+ (or something).\r
\r
and\r
\r
OSDN Git Service
