basictool is a command-line utility which can tokenise, de-tokenise, pack and analyse BBC BASIC programs for use with Acorn BBC BASIC on the BBC Micro and Acorn Electron.
BBC BASIC programs are tokenised by the interpreter when entered, and are usually saved and loaded in this tokenised form. This makes them hard to view or edit on a modern PC. basictool can tokenise and de-tokenise BBC BASIC programs:
$ # Start off with an ASCII text BASIC program, editable in any text editor.
$ cat test.bas
10PRINT "Hello, world!"
$ # Now tokenise it.
$ basictool -t test.bas test.tok
$ xxd test.tok
00000000: 0d00 0a15 f120 2248 656c 6c6f 2c20 776f ..... "Hello, wo
00000010: 726c 6421 220d ff rld!"..
$ # Note that test.tok is tokenised - there's no "PRINT" in xxd's output.
$ # If you transferred test.tok to a BBC Micro, you could LOAD it in the usual way.
$ # Now we have a tokenised BASIC program, we can demonstrate de-tokenising it.
$ basictool test.tok
10PRINT "Hello, world!"
$ # The previous command gave no output filename, so the output went to the terminal.
$ # But we can also de-tokenise to a file.
$ basictool test.tok test2.bas
$ # test2.bas is ASCII text BASIC, editable in any text editor.
$ cat test2.bas
10PRINT "Hello, world!"
(basictool doesn't care about file extensions; I'm using .bas and .tok here for text BASIC and tokenised BASIC respectively, but you can use any conventions you wish.)
You can also "pack" a program, making it significantly less readable but more compact:
$ cat test3.bas
square_root_of_49 = 7
my_variable = 42 + square_root_of_49
PRINT my_variable
$ # Note that test3.bas doesn't have line numbers; basictool will add them for us.
$ basictool -p test3.bas
1s=7:m=42+s:PRINTm
$ # basictool is happy to output the packed program as ASCII text, but it would
$ # usually make more sense to save it in tokenised form suitable for use with
$ # BBC BASIC.
$ basictool -p -t test3.bas test3.tok
$ xxd test3.tok
00000000: 0d00 0111 733d 373a 6d3d 3432 2b73 3af1 ...s=7:m=42+s:.
00000010: 6d0d ff m..
By specifying the "-v" (verbose) option twice when packing, additional information will be displayed during the packing process:
$ basictool -p -v -v test3.bas
info: input auto-detected as ASCII text (non-tokenised) BASIC
TOP=&0E54
@% [0]
my_variable [2] m
square_root_of_49 [2] s
TOP=&0E13
Bytes saved= 65
1s=7:m=42+s:PRINTm
basictool is really a specialised BBC Micro emulator built on top of lib6502. It runs an original BBC BASIC ROM and uses that to tokenise and de-tokenise programs. Programs are tokenised simply by typing them in at the BASIC prompt and de-tokenised simply by using the BASIC "LIST" command.
It also uses the Advanced BASIC Editor ROMs to provide the pack, unpack and analysis functions.
The standard BASIC abbreviations (such as "P." for "PRINT") can be used in text BASIC input to basictool.
Programs can be renumbered using the --renumber option. You can control the start line number and gap between line numbers using --renumber-start and --renumber-step if you wish.
This has exactly the same restrictions as BASIC's "RENUMBER", because that's really what it is. In practice it works well, but if your program is calculating line numbers in a RESTORE statement or other advanced trickery, renumbering is likely to break it.
Line numbers are optional in text BASIC input; basictool will automatically generate them if they're not already present.
If you need to number some lines, such as DATA statements which will be used with RESTORE, you can give line numbers on just those lines:
$ cat test4.bas
PRINT "Hello, ";
RESTORE 1000
READ who$
PRINT who$;"!"
PROCend
END
DATA clouds, sky
1000DATA world
DEF PROCend
PRINT "Goodbye!"
ENDPROC
$ basictool test4.bas
1PRINT "Hello, ";
2RESTORE 1000
3READ who$
4PRINT who$;"!"
5PROCend
6END
7DATA clouds, sky
1000DATA world
1001DEF PROCend
1002PRINT "Goodbye!"
1003ENDPROC
This will fail if the line numbers you provide would clash with the automatically generated line numbers; I suggest using large round values in order to avoid this being a problem.
If you don't like the line numbers generated by the automatic line numbering, you can use the --renumber option to tidy things up.
(Automatic line numbering works exactly the same as in beebasm's PUTBASIC command, if you're already familiar with that.)
Two different styles of "pretty-printed" formatted output are available.
I'll use this simple program to demonstrate:
$ cat test5.bas
FOR I=1 TO 100
FOR J=1 TO 100
PRINT I*J:IF I+J>42 THEN PRINT "Foo!":FOR K=1 TO 100:NEXT
NEXT
NEXT
The first option is BASIC's own LISTO command. LISTO 7 is probably the most useful here:
$ basictool --listo 7 test5.bas
1 FOR I=1 TO 100
2 FOR J=1 TO 100
3 PRINT I*J:IF I+J>42 THEN PRINT "Foo!":FOR K=1 TO 100:NEXT
4 NEXT
5 NEXT
The second option is the Advanced BASIC Editor's "format" utility:
$ basictool -f test5.bas
1 FOR I=1 TO 100
2 FOR J=1 TO 100
3 PRINT I*J:
IF I+J>42
THEN PRINT "Foo!":
FOR K=1 TO 100:
NEXT
4 NEXT
5 NEXT
You can "unpack" a program, adding additional spaces and breaking apart multi-statement lines, in order to make it more readable:
$ cat test7.bas
10foo=42:bar=7
20IFfoo+bar=49THENPRINT"7^2!":bar=8ELSEbar=4
30PRINTbar-foo
$ basictool -u test7.bas
10 foo=42
11 bar=7
20 IFfoo+bar=49 THEN PRINT"7^2!":bar=8 ELSEbar=4
30 PRINTbar-foo
Of course this isn't a perfect inverse of "pack", but it will help.
You may need to use the --renumber-step option to increase the gaps between line numbers in order for the unpack to succeed.
Note that --unpack is an output option rather than a transformation, so you can't (for example) unpack and tokenise or unpack and format at the same time. If you need to do this, you can call basictool a second time with the unpacked output as the input.
You can generate line number reference tables and variable cross-reference tables using the Advanced BASIC Editor's utilities. Obviously these are more useful with larger programs, but here's a simple demonstration:
$ cat test6.bas
10PRINT "Hello, ";:who$="world":end$="Goodbye!"
20GOTO 50
30PRINT "!"'end$
40END
50PRINT ;who$;
60GOTO 30
$ basictool --line-ref test6.bas
30 ( 60)
50 ( 20)
$ basictool --variable-xref test6.bas
@% [0]
end$ [2] 10 30
who$ [2] 10 50
$
There are a few options not described here which just provide ways to tweak basictool's behaviour. Use:
$ basictool --help
to see all the options. The man page provides full documentation; the link is to a pre-formatted PDF, but the original can be found in the man directory.
I developed basictool on Linux, but the code does not use any platform-specific features and should build with few or no changes on any operating system with a C99 compiler.
The simplest option is to download a release zip file from the releases page; it's probably best to pick the most recent. Unzip that somewhere using your favourite tool. If you prefer, you can "git clone" this repository and check out the branch or tag of interest.
If you're on a Unix-like system, you should just be able to do:
$ cd src
$ make
This will create a basictool executable in the top-level project directory, i.e. the one above src. The executable is self-contained and can be copied to wherever you want to install it.
The makefile contains simple support for cross-compilation, which is enough to build a Windows basictool executable using a Unix-like system:
$ sudo apt-get install gcc-mingw-w64-x86-64
$ cd src
$ TARGETCC=x86_64-w64-mingw32-gcc make
If you're not on a Unix-like system you may need to create your own build script or project file for your IDE. src/Makefile may be a good starting point; alternatively there is a simple shell script src/make.sh which will perform a build and it may be easiest for you to translate that into your platform's equivalent of a shell script. If you do this, please consider sending me the results so I can add them and make it easier for other people to build on your platform.
On Windows, to build with the Visual Studio compiler, you should be able to run src/make.bat from a native tools command prompt.
If you have problems or suggestions for improvement, you can raise an issue or submit a pull request in github. Alternatively you may like to post in the basictool thread on the stardot forums.
-
BBC BASIC was (of course) originally published by Acorn. The BASIC 4r32 ROM in the roms directory was downloaded from J. G. Harston's mdfs.net.
-
The BASIC editor and utilities were originally published separately by Altra. The Advanced BASIC Editor ROMs used here are (C) Baildon Electronics. The Advanced BASIC Editor ROM images in the roms directory were posted to stardot by J. G. Harston. Thanks to Dave Hitchins for his support for developing basictool using these ROMs.
-
6502 emulation is performed using lib6502. This was originally written by Ian Piumarta, but the versions of lib6502.[ch] included here are taken from PiTubeClient.
-
Cross-platform command line parsing (cargs.[ch]) is performed using cargs.
- v0.01:
- Initial release
- v0.02:
- Fix build error on gcc 10. Thanks to scruss for reporting this.
- v0.03:
- Add --unpack. Thanks to Dave Hitchins for the suggestion.
- Don't open the output file until we're about to write to it; this will avoid occasionally creating a zero-length output when an error occurs.
- v0.04:
- No code changes, but ROMs are now included in the github repository.
- v0.05:
- Get rid of --keep-spaces-start and --keep-spaces-end; BASIC 4 always strips trailing spaces anyway so --keep-spaces-end didn't work, and if we can only control stripping at the start of lines we only need the -k/--keep-spaces option.
- Warn if --keep-spaces is used when it has no effect.
- Warn if --pack-singles-n is used when it has no effect.
- Add man page.
- v0.06:
- Add support for using either BASIC 2 or BASIC 4. Thanks to lurkio for the suggestion.
- Preserve spaces by default as much as possible; get rid of --keep-spaces as this is now the default and add --strip-spaces*. Thanks to lurkio for the suggestion.
- Allow user-specified line number 0. Thanks to TobyLobster for reporting this.
- v0.07:
- When using both --pack and --renumber, renumber before as well as after packing. Thanks to lurkio for discovering the need to do this sometimes.
- v0.08:
- Fix off-by-one error causing some acceptable lines of text BASIC to incorrectly generate a "line too long" error. Thanks to lurkio for reporting this.
- v0.09:
- Add simple cross-compilation support to the makefile. Thanks to Ken Lowe for help with this.
- Fix build error on Ubuntu 22.04. Thanks to shifters67 for reporting this.
- lib6502: fix Z flag after ASL instruction. Thanks to dp11 for the fix.
- lib6502: fix _zpr not displaying zp location. Thanks to dp11 for the fix.
- Fix potential buffer overflow when in mpu_dump(). Thanks to dp11 for the fix.
- Add PDF version of man page.
- v0.10:
- Improve auto-detection of tokenised BASIC. Thanks to Tom Seddon for the bug report and new detection algorithm (taken from BeebLink).
- Improve accuracy of output with --ascii when detokenising BASIC containing embedded control codes. Thanks to Tom Seddon for reporting these problems.
- Add --output-binary option so users can optionally avoid embedded line feed control codes in tokenised BASIC being mangled when detokenising.
- Add manpage target to Makefile.
- Add src/make.bat to build with Visual Studio on Windows. Thanks to Tom Seddon for this.
- Make test suite run correctly on Windows (using git bash). Thanks to Tom Seddon for this.
- v0.11:
- Preserve the first line number even if it's >255. Thanks to lurkio for reporting this.