From: jpeters@wet.COM (John A. Peters)
Newsgroups: comp.lang.forth
Subject: cataloging all forth words
Date: 22 Jul 92 03:28:35 GMT
Organization: Wetware Diversions, San Francisco

MASTER.CAT  Revised on 7-19-92
by John A. Peters  415-239-5393  Jpeters@wet.com



            MASTER CATALOGUE

I have begun indexing all major forth words in all systems that are
available to the Berkley FIG chapter.  We have set up a BBS in Novato
that is dedicated to Forth.  It will be the depository for the index
of Forth words.  It is able for computer searching.

The typical record will have fields similar to those found in the
public library.  Think of one of the Dewei decimal system cards in the
hardwood file cabinet.  I am sure you all have seen it.  It has
several catagories of information and a short description of the book.



            DATA FIELDS OF INTEREST

00 ANSI Paragraph number if the word is listed.

01 Title i.e. Name of Forth word or module.

02 Author'(s)
    a) Creator of the concept or Client who needed the word.
    b) Author of the specification or grant request.
    c) Implementer's name and the date (The programmer)
    d) Systems analyst and alpha tester.
    e) Others who helped..

03 Date of inception (Birth date)

04 Date the code started working.

04 Testing agency, reports and date.

06 Users:
    a) Who have downloaded the source.
    b) Who state they are willing to help.
    c) Those who have sent thanks.
    d) Those who have sent suggestions for the want list.
    e) Those who have joined the E-Mail list for updates.
    f) Those users who have donated time, money or hardware.

07 Version(s) of Forth used.

08 Standard compliance: ie ANS, 83, 79, 77, FIG etc.

09 Exceptions to the standard.

10 Dependancys.

11 Prerequsites.

12 Comments:
   Add your feelings as to the value of the word.

13 Suggestions list and want lists.

14 Score card like that done by software magazines.



            METHOD OF DISTRIBUTION

Electronic mail on line on the "Programmable BBS".  There will be a
"master catalogue" on line.  Entries will consist of:


  1) The name of the forth word
  2) The stack comment
  3) A path to the source of the word on the hard disk.
  3) A path to the card catalogue entry in the data base.



            A SAMPLE LINE FROM THE CATALOGUE

BLOCK  ( n -- address )         19       C\F83\KERNEL.BLK
SED    ( -- )                    7  4    C\FPC\SRC\ED.SEQ

As you can see, the path reveals the version of forth, as well as the
file name and line or screen number.

There will be a word like VIEW <word> that will list the source for
the word.  The caller can down load (or compile) the source lines or
the whole file.  Comments will be requested for inclusion in the the
data base online.

I need suggestions on how to tie in the data base mentioned above.


Downloads histories will be posted to the data base so that interested
parties can find the names of others interested in particular words or
catagories of Forth.

By studying others use of Forth words Forth programmers will be able
to learn how their code is being put to use.  Duplicated sections of
code will come to light.  Factoring will improve as preexisting
words come to light (prior art).


            CREATE INCOME FOR PROGRAMMERS

By making an an up to date geanoligy of forth words and systems, those
who wish to, may communicate thanks and good wishes to Forth Founding
Fathers who have provided the code that that we all use.  In fact if
you wish, you can offer support to authors whose work is helpfull.

The shareware concept can be put to use to create income for the FIG
chapter you work with or the author of Forth it's self.  I have
mentioned the concept of royalties or honoriam to Chuck Moore and he
said he does not expect to see any royalties, but he did not
discourage my ideas either.


            FEEDBACK SOLICITED

Do you have any thoughts flames or wishes?  :-)

Do you have some interesting historical data on Forth words two to get
us started?  Were you there when some of the early words were created?

John A. Peters

Newsgroups: comp.lang.forth