[comp.lang.forth] OLIS - update - ***** Articles Neede *****

trolfs@vax1.tcd.ie (Tommy) (08/01/89)

    Firstly, thanks to everyone who responded to the OLIS proposal.
    Your input and support was great. 

    Ok, so here's the update.(Warning: it's quite long) 

    1) OLIS will be implemented (*). At the moment though it will 
    only be semi-automated, but never the less it should do the job. 
    (I'm in the middle of writing the code to service requests.
    hopefully it should be ready soon).

    2) FEEDING TIME FOR OLIS:- OLIS is an information service and as
    such needs information if it is to work. Also, OLIS is a voluntary
    service, so donations of info are vital if it is to work.

      WHERE TO SEND ALL THESE GEMS OF INFO: 
               Send all submissions to TROLFS@vax1.tcd.IE, with 
            "For Olis" in the subject line.

      WHAT IS NEEDED:

                As I pointed out earlier, OLIS is aimed at those who
    are new to Forth and also people who have done a bit of Forth, but
    want to explore some more. Here is a list of things that OLIS
    needs to have, just so it can start to be a service.

    * Books/papers lists:
                     BOOKS ON FORTH             (casual reading)
                     BOOKS ON LEARNING FORTH    (ie "Starting Forth")
                     BOOKS OOP and OOF
                     ADVANCED BOOKS ON FORTH


    These are just a few I can think of. If I have left out something 
    which you think should be included, then let me know. I have the 
    mailing catalogue from FIG. Can anyone tell me if it is ok to
    reproduce it for OLIS? 

         
    * "Forth For Your Computer" Catalogues:

                     WHAT'S AVAILABLE FOR YOUR AMIGA
                      "        "       "    "  PC
                      "        "       "    "  <whatever>
                        and so on... 
    If you are using a package on your computer then send in a review
    of it.

    * "Forth in the Real World":

    Want articles about what Forth has been and is being used for 
    (ie if you are using Forth for a real application then write a 
    few words about it and send it in). Also, I'm in the process of 
    writing a few articles on Forth for the Commodore User Group I'm 
    in, so this info would be doublely useful.
     

    Well, that's all I can think of for the moment. If you think of 
    something that would add to the service, then mail me. I have
    already received two good suggestions (from John White). They are:

    * A library of usefully words, and example code.

           On of the problems with Forth (if you don't use it
    frequently) is the re-inventing of the wheel every time you start
    something new. So, what are useful words to have around? The idea 
    of the library would be to answer this question by providing 
    specifications for just such useful words. Now DON'T send me the
    source code to your own personal libraries of useful words. What I
    want is just the SPECIFICATIONS, not the code. Also, I would like
    submissions in this layout (if possible):

      Name:     <name of word set>
      Brief:    <short description of word set>

      Vlist:    <list of word names, in implementation order if possible>

      Verbose: 
                <Description of each word, separately> 
    
     The descriptions should be in the following format:

       <name>       <effect on stack>
      
            <Description, comments and, if necessary, pseudo code> 

    eg.

          Name: General Null Terminated Strings Manipulation Library
          Brief: Some useful words for processing strings which are
                 stored in the NULL terminated format.

          Vlist:  NULL
                  $LEN
                  .
                  . 
                  .

          Verbose: 

            NULL        ( --- NULL)
               Places a NULL character on the stack.

            $LEN        (Addr --- LEN)
               returns the length of the string whos start address is
            on the stack.
                                .
                                .

                                .

           
                                .
     

    I think the library idea is great and will really help new and
    intermediate (ME!) Forthers a lot! So, make some time and send in
    your favourite words. Maybe we can chalk up some real nice (and
    useful) libraries. How about it?


    * The second proposal was to have a reference book for "Points of
        Style".

       This would be very useful in helping people write good code, 
    ie Dos and Don'ts. I know many would say that there are no correct 
    ways to write Forth code, but some are better than others and some 
    are just plain bad. So, let me know about programming practises which 
    turn you off and which ones appeal to you. I'll compile a chart of
    the 20 or 40 worst practises.
       


    I think this posting has go on long enough, so I'll wrap up
    quickly. Send ideas,comments and especially submissions to
    TROLFS@vax1.tcd.ie with "For OLIS" in the subject. Remember that
    OLIS will only be as good as it gets, so DO send in any useful scraps
    of info, or even spend a bit of time on writing something from your own
    experience. If you are responding to someones query on the net,
    then send a copy of the reply (plus question) to OLIS. I'll keep 
    everyone posted on developments. Till then.... :-)


    (*) OLIS will be implemented under my account, "TROLFS", and is in
    no way connected with Trinity College Dublin (TCD). If you have
    any questions or problems with OLIS, send them to me only, at
    TROLFS@vax1.tcd.ie. Thanks.
-- 
 Tommy                                       E-mail: trolfs@vax1.tcd.ie 
                   //  Amiga 500.
                \\//     What's your's called?         $P-)
-----------------\X-----------------------------------------------------
"Even if you're on the right track, you'll get run over if you just sit there."
-- Will Rogers