Sol BASIC tokenized file - Revision history

Dan Tobias: /* Software */

2013-09-10T23:18:04Z

‎Software

Dan Tobias: /* Extended BASIC tokens */

2013-01-24T02:20:22Z

‎Extended BASIC tokens

Dan Tobias: /* BASIC-80 tokens */

2013-01-24T02:20:02Z

‎BASIC-80 tokens

Dan Tobias: /* Documenting the format */

2013-01-11T01:54:17Z

‎Documenting the format

Dan Tobias: /* BASIC-80 tokens */

2013-01-05T18:28:49Z

‎BASIC-80 tokens

Show changes

Dan Tobias: Add BASIC-80 tokens

2013-01-05T18:17:58Z

Add BASIC-80 tokens

Show changes

Dan Tobias at 03:54, 31 December 2012

2012-12-31T03:54:41Z

Dan Tobias at 03:53, 31 December 2012

2012-12-31T03:53:26Z

Dan Tobias at 03:52, 31 December 2012

2012-12-31T03:52:21Z

Dan Tobias at 02:15, 28 December 2012

2012-12-28T02:15:46Z

← Older revision		Revision as of 23:18, 10 September 2013
Line 582:		Line 582:

	* [http://www.sol20.org/solace.html Solace: Sol emulator for Windows]		* [http://www.sol20.org/solace.html Solace: Sol emulator for Windows]
		+	* [http://jsmess.textfiles.com/messloader.html?module=sol20 JSMESS in-browser emulator of Sol-20]
	* [http://sol20.org/programs.html#Utility Some utilities]		* [http://sol20.org/programs.html#Utility Some utilities]

@@ Line 448: / Line 448: @@
 |BE||190||EXIT
 |-
-|BF||181||RUN
+|BF||191||RUN
 |-
 |C0||192||LIST

@@ Line 182: / Line 182: @@
 |BE||190||
 |-
-|BF||181||
+|BF||191||
 |-
 |C0||192||

@@ Line 37: / Line 37: @@
 The lines starting with "C" and "H" appear to be part of the filesystem (which include the name the program was saved as, "PROG"), so any documentation on their format belongs in the [[Filesystem]] section (or would if they were the true tape format of a SOL-20 rather than just an emulated version that might differ). The "D" lines encode the program file data itself, as a series of hexadecimal digits. Take them in pairs to get the successive bytes of the tokenized BASIC file.
-It appears to be a series of program lines, separated by the carriage return character (hex 0D). The first byte of each line (each program line, that is; ignore the physical lines in the representation of the file and divide lines only at 0D bytes) represents the number of bytes the line takes up; you can quickly skip to the next line by going forward that number of bytes. The next two bytes are the line number, represented as a 2-byte unsigned integer (little-endian). Then follows the tokenized program code itself. [[ASCII]] printable characters represent themselves (in literal strings, variable names, and numeric constants, the latter of which are simply stored as the series of ASCII digits instead of being encoded as integer or floating-point numbers as some other BASICs do). Some symbols like the quote marks are also represented as their plain ASCII values, though others (such as the equal sign) have different token representations (apparently to signal that they are operators or functions with special meaning). The keywords of BASIC each have a byte (in the high-bit-set range from 80 to FF hex) representing them; for instance, 89 hex is "PRINT". All spaces other than ones within quoted strings are stripped, as they are unnecessary to the syntax. They are added back on listing the program.
+It appears to be a series of program lines, separated by the carriage return character (hex 0D). The first byte of each line (each program line, that is; ignore the physical lines in the representation of the file and divide lines only at 0D bytes) represents the number of bytes the line takes up; you can quickly skip to the next line by going forward that number of bytes. The next two bytes are the line number, represented as a 2-byte unsigned integer ([[Endianness|little-endian]]). Then follows the tokenized program code itself. [[ASCII]] printable characters represent themselves (in literal strings, variable names, and numeric constants, the latter of which are simply stored as the series of ASCII digits instead of being encoded as integer or floating-point numbers as some other BASICs do). Some symbols like the quote marks are also represented as their plain ASCII values, though others (such as the equal sign) have different token representations (apparently to signal that they are operators or functions with special meaning). The keywords of BASIC each have a byte (in the high-bit-set range from 80 to FF hex) representing them; for instance, 89 hex is "PRINT". All spaces other than ones within quoted strings are stripped, as they are unnecessary to the syntax. They are added back on listing the program.
 In this manner, it should be possible to build a list of all the tokens by writing a program that uses all of them and seeing how it ends up when saved.

@@ Line 4: / Line 4: @@
 |released=1976
 |image=Sol-screen.jpg
-|caption=Sol BASIC screen shot
+|caption=Sol BASIC screen shot (as simulated in Solace)
 }}

@@ Line 3: / Line 3: @@
 |subcat2=Tokenized BASIC
 |released=1976
 }}

@@ Line 5: / Line 5: @@
 }}
-'''Sol''' was a line of computers in the late 1970s, the most popular of which was the SOL-20. It was one of the S-100 bus computers of that era which, if you added a disk drive, could run the [[CP/M]] operating system, but was often used with cassette data storage instead. It had a version of the [[BASIC]] programming language (not in ROM; you had to load it). When you saved a BASIC program to tape or disk, you could add a parameter to the SAVE command to make it save the program as plain text, which was more suitable for transfer to other systems. However, the default save mode was the more compact (but less transferable) tokenized form. On cassette, the low-level format was [[Kansas City Standard data cassette|Kansas City standard]].
+'''Sol''' was a line of computers in the late 1970s, the most popular of which was the SOL-20. It was one of the S-100 bus computers of that era which, if you added a disk drive, could run the [[CP/M]] operating system, but was often used with cassette data storage instead. It had a version of the [[BASIC]] programming language (not in ROM; you had to load it). When you saved a BASIC program to tape or disk, you could add a parameter to the SAVE command to make it save the program as plain text, which was more suitable for transfer to other systems. However, the default save mode was the more compact (but less transferable) tokenized form. On cassette, the low-level format was [[Kansas City Standard data cassette|Kansas City standard]] (Or maybe [[CUTS]]?).
 == Documenting the format ==