Imported Upstream version 0.2.0+beta

[debian/yforth] / README

diff --git a/README b/README
index 95d5713794c56356831ce1f8c09278dd6150aa11..1ec1bdec42f5ccd06ec10653e143fd0c04e2a43b 100644 (file)
--- a/README
+++ b/README
@@ -1,4 +1,4 @@
-yForth? v0.1beta - READ THIS (AND ONLY THIS) TO GET yForth? RUNNING.
+yForth? v0.2+beta - READ THIS (AND ONLY THIS) TO GET yForth? RUNNING.
 
 0) Hello world!
 Here's a little file which will help you having yForth? running in few
@@ -23,11 +23,6 @@ In fact, you'll find that all the device dependent routines are grouped
 together in the file "udio.c". If you're using Turbo C, Borland C, or any
 compiler which supplies the "conio.h", you can define HAVE_CONIO in 
 your "config.h" file and go. 
-Note that even if in file "udio.c" you'll see some lines telling you:
-#ifdef HAVE_CURSES
-or similar, yForth? actually doesn't support CURSES library. I've decided to
-stop my work as soon as something machine depended that was too messy has 
-came around.
 
 2) Where does the name yForth? came from?
 I've been charmed by Forth since the first time I "played" with it, but 
@@ -58,17 +53,15 @@ type which allows having 32bit Cells. Using Turbo C that's not possible.
 Below data definition you'll have to change the maximum values of your
 system. See "limits.h".
 - terminal
-Finally, define HAVE_CONIO if you're using Turbo C, Borland C or GCC for DOS.
-You'll have some nice words such as "page"...
+Finally, define HAVE_CONIO to 1 if you're using Turbo C, Borland C or GCC 
+for DOS. You'll have some nice words such as "page"...
 - special functions
 "asinh", "acosh", "atanh" aren't provided by all the libraries, if you don't
-have them delete the definitions at the end of "config.h".
+have them reset the definitions at the end of "config.h".
 
-The second thing to do now is configuring the "Makefile". I know, it's rude,
-but yForth? is drifting on my system for too long, I want to finish it 
-within 1996.
-At the moment "Makefile" is ready for GCC (under Linux), it's simple and 
-you won't find any problem modifying it.
+The second thing to do now is configuring the "Makefile". At the moment 
+"Makefile" is ready for GCC (under Linux), it's simple and you won't find any 
+problem modifying it.
 
 Third, type "make all". Yes, that's all.
 
@@ -94,10 +87,6 @@ Don't forget:
        - yForth? is a "beta" release, I think it has bugs, but, most 
                important, I'm afraid that some words don't behave as the
                standard says they have to.
-       - yForth? comes with no warranty, I don't make any warranty about it.
-       - yForth? is completely free. You can use, modify, doing anything
-               you want with it. If you're going to use it in any project,
-               I would be grateful if you cite me, but you're no obliged.
        - yForth? is NOT a complete ANS Forth.
        - yForth? is written in ANSI C. Ok, you could see some warning while
                compiling it, and I've to check it with lint, but it 
@@ -119,12 +108,11 @@ I'll be very happy if you report me some bug. Obviously I'll be happy even
 more if you tell me how fo fix it, but I can't pretend so much, even 'cause
 my C is not very readable (few comments...).
 
-8) Who am I?
-Luca Padovani
-v. Cormons, 12
-48100 Ravenna (RA)
-Italy
-
 email: lpadovan@cs.unibo.it
 
 Enjoy yForth?
+
+**********************************************************************
+                             CONTRIBUTORS 
+**********************************************************************
+