2.5: first git version

INSTALL

@@ -0,0 +1,183 @@
+Basic Installation
+==================
+
+   These are generic installation instructions.
+
+   The `configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation.  It uses
+those values to create a `Makefile' in each directory of the package.
+It may also create one or more `.h' files containing system-dependent
+definitions.  Finally, it creates a shell script `config.status' that
+you can run in the future to recreate the current configuration, a file
+`config.cache' that saves the results of its tests to speed up
+reconfiguring, and a file `config.log' containing compiler output
+(useful mainly for debugging `configure').
+
+   If you need to do unusual things to compile the package, please try
+to figure out how `configure' could check whether to do them, and mail
+diffs or instructions to the address given in the `README' so they can
+be considered for the next release.  If at some point `config.cache'
+contains results you don't want to keep, you may remove or edit it.
+
+   The file `configure.in' is used to create `configure' by a program
+called `autoconf'.  You only need `configure.in' if you want to change
+it or regenerate `configure' using a newer version of `autoconf'.
+
+The simplest way to compile this package is:
+
+  1. `cd' to the directory containing the package's source code and type
+     `./configure' to configure the package for your system.  If you're
+     using `csh' on an old version of System V, you might need to type
+     `sh ./configure' instead to prevent `csh' from trying to execute
+     `configure' itself.
+
+     Running `configure' takes awhile.  While running, it prints some
+     messages telling which features it is checking for.
+
+  2. Type `make' to compile the package.
+
+  3. Optionally, type `make check' to run any self-tests that come with
+     the package.
+
+  4. Type `make install' to install the programs and any data files and
+     documentation.
+
+  5. You can remove the program binaries and object files from the
+     source code directory by typing `make clean'.  To also remove the
+     files that `configure' created (so you can compile the package for
+     a different kind of computer), type `make distclean'.  There is
+     also a `make maintainer-clean' target, but that is intended mainly
+     for the package's developers.  If you use it, you may have to get
+     all sorts of other programs in order to regenerate files that came
+     with the distribution.
+
+Compilers and Options
+=====================
+
+   Some systems require unusual options for compilation or linking that
+the `configure' script does not know about.  You can give `configure'
+initial values for variables by setting them in the environment.  Using
+a Bourne-compatible shell, you can do that on the command line like
+this:
+     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
+
+Or on systems that have the `env' program, you can do it like this:
+     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
+
+Compiling For Multiple Architectures
+====================================
+
+   You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory.  To do this, you must use a version of `make' that
+supports the `VPATH' variable, such as GNU `make'.  `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script.  `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.
+
+   If you have to use a `make' that does not supports the `VPATH'
+variable, you have to compile the package for one architecture at a time
+in the source code directory.  After you have installed the package for
+one architecture, use `make distclean' before reconfiguring for another
+architecture.
+
+Installation Names
+==================
+
+   By default, `make install' will install the package's files in
+`/usr/local/bin', `/usr/local/man', etc.  You can specify an
+installation prefix other than `/usr/local' by giving `configure' the
+option `--prefix=PATH'.
+
+   You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files.  If you
+give `configure' the option `--exec-prefix=PATH', the package will use
+PATH as the prefix for installing programs and libraries.
+Documentation and other data files will still use the regular prefix.
+
+   In addition, if you use an unusual directory layout you can give
+options like `--bindir=PATH' to specify different values for particular
+kinds of files.  Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.
+
+   If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+Optional Features
+=================
+
+   Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System).  The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+   For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+Specifying the System Type
+==========================
+
+   There may be some features `configure' can not figure out
+automatically, but needs to determine by the type of host the package
+will run on.  Usually `configure' can figure that out, but if it prints
+a message saying it can not guess the host type, give it the
+`--host=TYPE' option.  TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name with three fields:
+     CPU-COMPANY-SYSTEM
+
+See the file `config.sub' for the possible values of each field.  If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the host type.
+
+   If you are building compiler tools for cross-compiling, you can also
+use the `--target=TYPE' option to select the type of system they will
+produce code for and the `--build=TYPE' option to select the type of
+system on which you are compiling the package.
+
+Sharing Defaults
+================
+
+   If you want to set default values for `configure' scripts to share,
+you can create a site shell script called `config.site' that gives
+default values for variables like `CC', `cache_file', and `prefix'.
+`configure' looks for `PREFIX/share/config.site' if it exists, then
+`PREFIX/etc/config.site' if it exists.  Or, you can set the
+`CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all `configure' scripts look for a site script.
+
+Operation Controls
+==================
+
+   `configure' recognizes the following options to control how it
+operates.
+
+`--cache-file=FILE'
+     Use and save the results of the tests in FILE instead of
+     `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
+     debugging `configure'.
+
+`--help'
+     Print a summary of the options to `configure', and exit.
+
+`--quiet'
+`--silent'
+`-q'
+     Do not print messages saying which checks are being made.  To
+     suppress all normal output, redirect it to `/dev/null' (any error
+     messages will still be shown).
+
+`--srcdir=DIR'
+     Look for the package's source code in directory DIR.  Usually
+     `configure' can determine that directory automatically.
+
+`--version'
+     Print the version of Autoconf used to generate the `configure'
+     script, and exit.
+
+`configure' also accepts some other, not widely useful, options.
+

LICENSE

@@ -0,0 +1,19 @@
+Copyright (c) 1999-2018 Michael Haardt
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

Makefile.in

@@ -0,0 +1,113 @@
+srcdir=		@srcdir@
+VPATH=		@srcdir@
+prefix=		@prefix@
+exec_prefix=	@exec_prefix@
+datarootdir=	@datarootdir@
+localedir=	@localedir@
+
+CC=		@CC@
+RANLIB=		@RANLIB@
+CFLAGS=		@CFLAGS@
+CPPFLAGS=	@CPPFLAGS@ -DLOCALEDIR=\"$(localedir)\"
+LDFLAGS=	@LDFLAGS@
+LIBS=		@LIBS@
+
+CATALOGS=	de.mo
+
+all:		bas all-po-@USE_NLS@
+all-po-no:
+all-po-yes:	$(CATALOGS)
+
+bas:		main.o libbas.a getopt.o getopt1.o
+		$(CC) -o $@ $(LDFLAGS) main.o libbas.a getopt.o getopt1.o $(LIBS)
+
+token.c:	token.l token.h
+		flex -i -t token.l >token.c
+
+libbas.a:	auto.o bas.o fs.o global.o token.o program.o \
+		str.o value.o var.o
+		rm -f $@
+		ar cq $@ auto.o bas.o fs.o global.o token.o program.o \
+		str.o value.o var.o
+		@RANLIB@ libbas.a
+
+cppcheck:
+		cppcheck $(CPPFLAGS) -q --enable=all .
+
+install-po:	install-po-@USE_NLS@
+install-po-no:
+install-po-yes:	$(CATALOGS)
+		for cat in $(CATALOGS); do \
+		  dir=$(localedir)/`basename $$cat .mo`/LC_MESSAGES; \
+		  [ -d $$dir ] || @INSTALL@ -m 755 -d $$dir; \
+		  @INSTALL@ -m 644 $$cat $$dir/bas.mo; \
+		done
+
+check:		bas
+		for i in test/test*; do ./$$i || break; done
+
+install:	all
+		@INSTALL@ -m 755 -d @bindir@
+		@INSTALL@ bas @bindir@/bas
+		@INSTALL@ -m 755 -d @libdir@
+		@INSTALL@ -m 644 libbas.a @libdir@/libbas.a
+		@RANLIB@ @libdir@/libbas.a
+		@INSTALL@ -m 755 -d @mandir@/man1
+		@INSTALL@ -m 644 bas.1 @mandir@/man1/bas.1
+		make install-po
+
+.c.o:
+		$(CC) -c $(CPPFLAGS) $(CFLAGS) $<
+
+.SUFFIXES:	.po .mo
+
+.po.mo:
+		msgfmt -o $@ $<
+
+*.po:		bas.pot
+		for cat in *.po; do \
+		  if msgmerge $$cat bas.pot -o $$cat.tmp; then \
+		    mv -f $$cat.tmp $$cat; \
+		  else \
+		    echo "msgmerge for $$cat failed!"; \
+		    rm -f $$cat.tmp; \
+		  fi; \
+		done
+
+bas.pot:	[a-b]*.[ch] [e-s]*.[ch] v*.[ch]
+		xgettext --add-comments --keyword=_ [a-b]*.[ch] [e-s]*.[ch] v*.[ch] && test -f messages.po && mv messages.po $@
+
+bas.pdf:	bas.1
+		groff -Tps -t -man bas.1 | ps2pdf - $@
+
+#{{{script}}}#{{{ clean
+clean:
+		rm -f *.out core token.c *.o libbas.a *.mo
+#}}}
+#{{{ distclean
+distclean:	clean
+		rm -rf autom4te.cache bas config.cache config.h config.log config.status configure.lineno Makefile bas.1 test/runbas
+#}}}
+#{{{ tar
+tar:		bas.pdf distclean
+		(b=`pwd`; b=`basename $$b`; cd ..; tar zcvf $$b.tar.gz $$b/LICENSE $$b/INSTALL $$b/Makefile.in $$b/README $$b/NEWS $$b/configure $$b/install-sh $$b/test $$b/[a-z]*.*)
+#}}}
+#{{{ dependencies
+auto.o:	auto.c config.h auto.h programtypes.h var.h value.h str.h token.h autotypes.h program.h
+bas.o:	bas.c config.h getopt.h auto.h programtypes.h var.h value.h str.h token.h autotypes.h \
+	 program.h bas.h error.h fs.h global.h statement.c statement.h
+fs.o:	fs.c config.h fs.h str.h
+getopt.o:	getopt.c config.h getopt.h
+getopt1.o:	getopt1.c config.h getopt.h
+global.o:	global.c config.h auto.h programtypes.h var.h value.h str.h token.h autotypes.h \
+	 program.h bas.h error.h fs.h global.h
+main.o:	main.c config.h getopt.h bas.h
+program.o:	program.c config.h auto.h programtypes.h var.h value.h str.h token.h autotypes.h \
+	 program.h error.h fs.h
+statement.o:	statement.c config.h statement.h
+str.o:	str.c config.h str.h
+token.o:	token.c config.h auto.h programtypes.h var.h value.h str.h token.h autotypes.h \
+	 program.h statement.h
+value.o:	value.c config.h error.h value.h str.h
+var.o:	var.c config.h error.h var.h value.h str.h
+#}}}

NEWS

@@ -0,0 +1,14 @@
+Changes compared to version 2.4
+
+o  truncate bug fixed
+o  Multi line if with hanging comment works now
+o  Add files command
+o  Fixed bug in expression parser
+o  OPTION BASE bug fixed
+o  Matrix inversion test improved
+o  WIDTH 0 bug fixed
+o  Missing error check on multi assignments added
+o  Wrong FOR loop management fixed
+o  Replaced wrong int assignment with long assignment for integers
+o  unnum bugs fixed
+o  HP-UX build works again

README

@@ -0,0 +1,35 @@
+Bas is an interpreter for the classic dialect of the programming language
+BASIC.  It is pretty compatible to typical BASIC interpreters of the 1980s,
+unlike some other UNIX BASIC interpreters, that implement a different
+syntax, breaking compatibility to existing programs.  Bas offers many ANSI
+BASIC statements for structured programming, such as procedures, local
+variables and various loop types.  Further there are matrix operations,
+automatic LIST indentation and many statements and functions found in
+specific classic dialects.  Line numbers are not required.
+
+The interpreter tokenises the source and resolves references to variables
+and jump targets before running the program.  This compilation pass
+increases efficiency and catches syntax errors, type errors and references
+to variables that are never initialised.  Bas is written in ANSI C for
+UNIX systems.
+
+Please do "make check" after compiling bas to run a couple regression
+tests.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.