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
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
binary tree dictionary structure. The direct-threading mechanism uses\r
the direct-page addressing mode of the 6809, and thus may not be easily\r
adaptable to FORTH-83. It also uses absolute addressing, and thus does\r
-not comform to the requirements of OS-9. (I am working on an\r
-indirect-threaded version of BIF for OS-9 in my spare time.)\r
+not comform to the requirements of OS-9. (I was working on an\r
+indirect-threaded version of BIF for OS-9 in my spare time, it \r
+has not happened at this point.)\r
\r
BIF.BIN is the executable object; after LOADMing it, EXEC the address\r
-&H1300 (see below). BIFSOURC.ARC contains the archived (TC31) source\r
-files; the assembler used is Disk EDTASM+. I used TSEdit to generate\r
-the source files in EDTASM+ format:\r
+&H1300 (see below). The assembler used is Disk EDTASM+. I used TSEdit \r
+to generate the source files in EDTASM+ format:\r
\r
line-number SPACE [label] TAB mnemonic etc. LF\r
\r
-Using a text editor to replace the macros with their expansions should\r
-make it compatible with most other assemblers. An object which will run\r
-under the EDTASM+ "stand-alone" debugger may be generated by changing\r
-ORG $1200 in BIF.ASM to ORG $3F00.\r
+Using a text editor (etc.) to replace the macros with their expansions \r
+should make it compatible with most other assemblers. An object which \r
+will run under the EDTASM+ "stand-alone" debugger may be generated by \r
+changing ORG $1200 in BIF.ASM to ORG $3F00.\r
\r
-BIFSCREE.ARC contains the BIF/FORTH source for several utilities, the\r
+The archive contains the BIF/FORTH source for several utilities, the\r
assembler, and double integer definitions (TOOLS.G00) and a definition\r
pairing example (PAIRS.G28) useful for making paired lists. Using\r
TOOLS.G00 and PAIRS.G28 directly will require moving the two files to\r
with the whitespace will move the source code out of alignment with the\r
physical FORTH/BIF screens, and thus cause the source code not to load.\r
\r
-If you want to look at these two files with an editor, I suggest copying\r
-them to a different disk and looking at the copies. Even my favorite\r
-IBM PC editor, QEDIT, will insert a CR/LF at the end of every 512 bytes\r
-on saving, which is not good. (I wonder how many letters from OS-9\r
-users it would take to convince the folks at SEMWARE/Applied Systems\r
-Technologies to make an OS-9 version of their editor?)\r
-\r
-For $5.00, to cover postage, time, and the cost of floppies, I will send\r
-a copy of the BIF screens disk on a standard 5 1/4" (ECB formatted)\r
-floppy. If you request the EDTASM+ compatible source code, I will send\r
-that as well, on the same format disks. For $5.00 more, I will include\r
-a photo-copy of the documentation (useful if you don't have a way to\r
-print it).\r
+If you want to look at these two files with an editor, use the 32col.c\r
+program to look. At present, I have no means of converting them back.\r
+\r
+If you want to send me money, that sounds great, but contact me by \r
+e-mail first.\r
\r
The documentation which follows is written in the standard FORTH\r
documentation style. It is not intended as a primer or study guide.\r
Information about BIF as of April 2019.\r
\r
Joel Matthew Rees, Amagasaki, Hyogo, Japan.\r
- joel.rees@gmail.com\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
Copyright 2000, 2019 Joel Matthew Rees\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
