BASIC Accelerator Ver. Rev.1 (2024.02.13)


BASICAcc is a Full BASIC to Object Pascal translator.
Translated programs shall be executed using FPC + Lazarus.
Numerical operation shall be considerably faster than Binary mode of Decimal BASIC.
This verision is applicable for Lazarus 1.6.4 ~2.2.6.

Revision History
Ver. Rev.1
Fixed the falt on CONFIRM$, which was not invoked synchronously.
Fixed the bug numeric variables were not initialied properly on the decimal mode.
Ver. Rev.3
End of Line determined by default for true files.
Ver. Rev.2
Fixed the fault that a numeric value was outputed without a trailing space in the Decimal mode.
Ver. Rev.1
Fixed the bug on READ statements which read to string variables.
Fixed the fault on the autoformat routine of the editor.
Fixed the bug that MAT READ for interal files on the complex mode did not work.
Fixed the fault that non-fatal exceptions were not reported.
Made intenal files serve on the complex mode.
Fixed the fault that columns were not diplayed correctly.
Add CDECL option to MOUSE POLL statements.
Fixed the fault that closing the child window yielded freezing or abnormal termination on Linux.
Increased the performance on MOUSE POLL statements on Linux.
Fixed the bug LINE STYLE interfered PLOT AREA.
Fixed the issues on printing.
Fundamental part imported from Ver. 2.1
Program execution thread separated from the GUI thread .
Fixed the bug that MAT statements caused Access Violation when DEBUG ON and TRACE OFF.
Modified the behavior of CHARACTER INPUT NOWAIT.
Fixed the fault that CLOSE for an inactive channel caused an exception.
Fixed the fault that array parameters of functions caused memory leak.
"-B" added into the command line for programs with modules.
On generating 64 bit code, set to use SSE4.1 instructons if available.
Corrected the behaivior of READ IF MISSING when DATA stataments have an incomplete number of items.
Corrected the behaivior of file input statements on exceptions raising.
Modulated automatic correction.
Adjusted for Lazarus 1.8.0.
Fixed the bug LOCATE VALUE(12) reflexed LOCATE VALUE(2).
Increased the maximum number of LOCATE VALUE silide bars.
Fixed the bug on execution of PRINT statemetns.
Fixed the bug on Find & Replace menus.
Fixed the bug SET ZONEWIDTH could not have a variable in parameter.
Fixed the bug on WAIT DELAY.
Adapted to FPC3.0.2+Lazarus1.6.4.


Set up (Lazarus)

Download Win32 Lazarus2.2.6 and install it into the folder that has no space characters on its path name.
Lazarus Download (SourceForge)

Set up (BASICAcc)

BASICAcc should be extracted into a regular folder on which the user has write permission.
The name of the folder must not contain any space characters.
For example, Desktop may not be suitable. USB flush drives shall be suitable.
When the system is updated by overwriting, the OUTPUT folder must be cleared.
Afterward, execute BASICAcc.exe, and set up two paths.
Click "Set Up" and select "Path".
"fpc path" is the path to the folder on which fpc.exe exists.
"Lazarus path" is the full path name of the folder "lazarus".

IF you have installed win32 Lazarus + fpc 3.0.4 on C drive, the two paths are following.


If you use 64 bit Windows, Lazarus win64 also can be used.
Lazarus Win64
Select Setup - Path menu to set Target CPU to 64bit and set the paths.
When you use lazarus-1.8.4-fpc-3.0.4-win64.exe, for instance, the fpc path is like as follows.
However when cros-x86_64 add-on is installed to 32 bit Lazarus, the fpc path is same as the path to 32 bit fpc.
Since FPC does not support 80 bit extended precision floating point arithmetic on Win64, power operation, some transcendental functions, MAT INV statement and DET function or so may perform inaccurate.
If you require accuracy on 64bit code, use Linux 64bit version.

Linux (x86_64)

Set up (fpc and Lazarus)

Download and install fpc 3.2.2, fpc-src 3.2.2 and Lazarus 2.2.6 from
Lazarus x86_64 RPM,
Lazarus AMD64 DEB.
BASICAcc works on Lazarus 1.6.4 to 3.0.0, but lazarus 1.8.0 ~2.0.6 cannot handle AREA STYLE.

Set up (BASICAcc)

Download BASICAcc1213Rev1_Linux64.tar.xz.
This system must be installed into the folder on which the user has write permission.

On Cent OS 7, FPC 3.0.4 does not work properly. Try FPC 3.0.2 + Lazarus 1.6.4.
See Lazarus Forum


Can't find unit fileutil
When you see this error, modify Lazarus Path on the SetUp menu.
Folders such as components and units are put on the folder that the Lazarus Path directs.
That may as follows.


Set up(XCode Command Line Tools)

Install XCode Command Line Tools.
In the terminal, type
sudo xcode-select --install
sudo xcodebuild -license accept
Otherwise download "Command Line Tools for Xcode" from Apple Developer .
See Installing Lazarus on MacOS X.
See also Installing Lazarus on Mac OS X - Free Pascal(PDF)
Note. BASICAcc does not require GDB. So you do not have to install GDB.

Set up(fpc and Lazarus)

Install FPC 3.2.2 and Lazarus 2.2.6, downloading from Lazarus Download

Set up (BASICAcc)

This system should be installed into the folder on which the user has write permission.
And the folder must not contain a space character. Note that when you use a USB drive, if it has a name such as "NO NAME", it must be renamed.

Trouble Shooting
1. For the First Time
(1) Unabe to create file "/private/var/folders/……

Move BASICAcc icon ( into the Application folder or another location, and then run BASICAcc.
Once normally performed, can be retured into the original folder.
For details, search "App Translocation" on the internet.

(2) For the first tme, NoName must be executed by clicking with control-key pressed .

(3) Empty ReportForm shown
If the first Run comannd yields empty ReportForm, this may caused by Unexecuted XCode license agreement.
On the terminal, run sudo xcrun cc and enter agree at the end.

(4) ReportForm shows PPU Source :synedit.pp not found.
Launch Lazarus IDE and select Package menu - Open Loaded packages.
And then Open and Compile the followings:

(5) "do setup Lazarus Path" shown.
 Select path on the setup menu, and then rewrite Lazarus path correctly.
Lazarus path is
on Lazarus 2.0.6, but it is
on Lazarus 2.2.2 or later, while lazarus path was
on former versions.

Known Faults
MOUSE POLL statement does not work properly.
Behaviors of some graphics statements are no good as in Decimal BASIC Mac(Intel).


Language Specifications are in accordance with the Graphics module, the modules module, and the individual character input module of ISO Full BASIC .

Known Faults

EXTYPE,RETRY and CONTINUE do not work properly for exceptrions raised in an exception handler.


On the following cases, GOTO statements and IF-THEN-line_number statements can not be executed.
branches from inside to outside of when-body (i.e. inside of WHEN~USE)
branches from inside to outside of a DO block that contains a protection block that contains a EXIT DO.
branches from inside to outside of a FOR block that contains a protection block that contains a EXIT FOR.

If a routine (or the main program) has a when-in block that has an exception-handler containing a GOSUB~RETURN subroutine, the routine can not have a GOSUB~RETURN subroutine that is not contained in any protection block.

RETRY and CONTINUE do not work properly for exceptrions raised in exception handlers.

Parameters of PROGRAM or CHAIN statements should be simple variables (Arrays not allowed).

When an exception occurs while executing an INPUT or READ statement that has multiple variables, those variables remain all unchanged.

Maximum length declaration for string variables is ignored. (no cut off done.)

Incompatibilities with Decimal BASIC

Character Encoding

The character encoding is UTF-8.
This is a problem when non-ASCII characters such as © , µ , ° , ± , Ä or Æ are used.
ORD-functions and CHR$-functions are defined under Unicode.
File I/O assumes the character encoding is UTF-8.
Executing a line like
just after the execution of the OPEN-statement enables files of system default encoding to be read or written.
Even in such a case, the internal encoding remains to be UTF-8.
PRINT USING-statements and USING$-functions need the formatting characters as many as the byte length of the string.

If you want to manipulate byte files, you can change the internal character encoding to byte encoding by adding a line
into each program unit, or change the setting of "Unit of string manipulation" to "byte" in the Option Compatibility menu.
In such a case, no ANSI encoded non-ASCII characters can be displayed on the screen.

UTF-8 encoding slows some string manipulation such as s$(m:n).
If you use only ASCII 7-bit characters, consider to change the "Unit of string manipulation" to "byte" in the Option Compatibility menu.

Program Encoding

Programs shall be encoded to the system default encoding on saving and decoded on loading.
That is, program files have compatibility with Decimal BASIC.
If you want programs to be saved and loaded remaining the character encoding UTF-8, change the Editor Option setting in the Option menu.

CHAIN statements

A CHAIN statement launches a file of extension ".BAS" with file association. The destination programs shall not be compiled.
No CHAIN or EXECUTE statement can have array parameters.


Any BREAK statement will do, but it only breaks the program.


When GOSUB statements are used, each line must has a line number.

Bugs which Decimal BASIC has

Decimal BASIC has a fault that an internal procedure of the mainprogram can be invoked from an external procedure, but BASICAcc does not allow such a program.

Decimal BASIC Original Enhancement

DRAW MODE NOTXOR (MASK, MERGE, XOR),which are Decimal BASIC original enhancement, do not work properly.
On Mac, they are neglected. On Windows and Linux, then won't work until a PLOT LINES is executed.

The decimal 1000 digit mode and the rational arithmetic mode, which Decimal BASIC has, are also not avaialable.

The Microsoft BASIC compatible mode is not available.
Also Metafiles, OLE, ActiveX and CallBack functions are not available.

About System

The executable file is generated as 'NoName.exe' or 'NoName' in the 'output' folder. This can be renamed and used for the destination of a CHAIN statement.


This software is free software published under GPL.

If you noticed any bugs, report at
Decimal BASIC Open Source Project Open Discussion Forum

© 2018 SHIRAISHI Kazuo

Decimal BASIC home page

inserted by FC2 system