Hello, welcome to BogusForth v0.8.6
written by Antonio Maschio 2004 <tbin@libero.it>
This is free software with ABSOLUTELY NO WARRANTY.

USAGE
-----

(from the bf -h execution:)

Usage:
bf <options> <filename>

OPTIONS
-c	execute filename leaving C file filename.c
        *** NOT IMPLEMENTED YET ***
-h	give this help and exit
-V	show vocabulary in continuous mode
-v	show vocabulary by screens
-e	don't show error messages
-q	don't be verbose
With no filename, start in interactive mode.


CONTROL CONSTANTS
-----------------

The file bf.h sets up many variables that control the bf compilation
process. Let's review in full the ones you can change:

- RCNAME/WRCNAME control the name of the resources for bf. This option has
not been implemented yet, so you can leave them as they are.
- BUFFERNAME sets name of buffer file name. Set it to the name you prefer,
possibly with the .bf extension.
- ALBF sets name of the autoload file. Read in the following fo what about
autoload file. You can change to any file you want.
The name, though, shouldn't contain relative paths such as "~/.mybfal":
They won't work.
- BFEDITOR sets the name of the preferred editor. Choose the one you
prefer or insert the one you want.
- STACKMAX controls te depth of the stack. Change it if you need more
space (it's not a smart thing, though, since a stack structure takes
264 bytes for each stack location).
- MAXLINE controls the dimension of the input string. This leads to the
following table:

input string		MAX LENGTH
------------------------------
command line		MAXLINE-1
string "s"			MAXLINE-2
function [f]		MAXLINE-2

The other constants shouldn't absolutely be touched, unless you know
what you are doing.

THE WIN32 DEFINITION
--------------------

Win32 OSes are all driven under the WIN32 variable set. This means that
the compilation under Win32 or Unixes is different, in terms of
compilers and environment. In particular, snprintf and getcwd are
known under my 2.95 gcc compiler as _snprintf and _getcwd. In second
place, tools like less are not common under Windows. So win32 users
are adviced to download less.exe from the bf download page and
install it. Some minor differences involve the dir command, DIR under
win32 and ls under Unix.
If you compile bf under Unix, no surprises.
If you compile bf under win32, instead of using the precompiled version,
you may make sure if you have djgpp or minsys installed. So, ls.exe, cat.exe
and less.exe could always be already present. Even vi.exe, I wish.
In this case you could safely uncomment the #undef WIN32 line in bf.h
and gain the power of a Unix environment (though under Windows).


AUTOLOAD FILE
-------------

St the start, bf looks for a file named along the ALBF definItion
(bfal as default), and executes it.
Such a file is a collection of bf commands. You can:

- values or functions stored in particular variables;
- strings to be printed at start 
- values put on the stack
- see a file (command s)
- set active debug option (command z)
- set active write-to-buffer-file option (command ])
- any other thing bf can do. See it as a bashrc or an autoexec.bat
  file.

It's name may be changed (see above).

----------------

It's GPL: enjoy...
