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