Upstream changes:
Version 2.769, July 4, 2015
Fixing two bugs under Windows:
print color under windows handles single argument correctly
cpu extension sse2 is no longer required, so yabasic should run again on older hardware
Version 2.768, May 25, 2014
Fixing some bugs under Windows and Linux:
Core dump e.g. under Linux mint related with grafics
Problems with embedded newlines within the Windows console
Keys pressed within grafic window are not always reported to inkey$ (Windows-Version)
Spurios problems with colors under Windows and linux (reported but not fixed yet)
Remove the patch which included in upstream source
Upstream changes:
2.767 (March 15, 2014)
Fixed a bug which caused yabasic under Windows to freeze on syntax errors
2.766 (March 15, 2014)
Fixed some bugs related with ncurses under linux
2.765 (January 30, 2014)
Added support for later versions of ncurses and 64 bit Systems
Avoided forks for inkey$ under Unix
Fixed a bug related with break and continue
2.764 (January 22, 2014)
- Added support for later versions of ncurses and 64 bit Systems
- Avoided forks for inkey$
PR 46532 by Wen Heping.
While here, set LICENSE.
Version 2.762 (September 16, 2005)
- Swapped the precedence of unary minus and exponentiation to
follow the mainstream of programming languages. Suggested
by Mike Hoffman.
- Fixed a bug with drawing the outline of a triangle.
- Lots bugs and typos fixed in the docu. Thanx to A. Costa !
- rinstr() is okay again.
- system$() may not dump any longer, if an external command returns no output.
- Some improvements for compiling on FreeBSD.
- Made the text-command working again.
- Maybe yabasic does not leak resources under Windows 95 any longer.
- Some fixes related with the console window under Windows
- Added a list of reserved words to the documentation.
- Special thanks to Derek and Mike Huffmann !
Version 2.76 (April 25, 2005)
Some major improvements for grafics
- Full color support !
- Different fonts for the text-command
- The new command triangle
Version 2.75 (May 19, 2004)
- Yabasic finally has an Icon under Windows
- The str$()-function, may now format numbers
like 123,456.56 (or 123.456,56 for german conventions)
- Changed the system()-function under Windows
to use the right command-processor
- Added a list of command, grouped by topics to the
documentation
- Yellow is no longer brown under windows
- Removed a security problem related with printing
under Unix
- Programs, that import libraries can now be
bound, including all the imported libraries
Version 2.740 (January 18, 2003)
- Implemented the bind-feature
- More verbose messages on failing open-calls
Version 2.730 (August 19, 2003)
- Complete rewrite of the documentation
- Updated my system, which introduced new
versions of the toolchain (gcc, autoconf, ...)
- No changes in yabasic itself
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
curses.buildlink2.mk. This was wrong because we _really_ do want to
express that we want _n_curses when we include the buildlink2.mk file.
We should have a better way to say that the NetBSD curses doesn't
quite work well enough. In fact, it's far better to depend on ncurses
by default, and exceptionally note when it's okay to use NetBSD curses
for specific packages. We will look into this again in the future.
with some minor modifications by me.
Yabasic implements the most common and simple elements of the basic language;
It comes with goto/gosub, with various loops, with user defined subroutines
and Libraries. Yabasic does monochrome line graphics and printing.
Yabasic runs under Unix and Windows; it is small (around 200KB) and free.
