STOS.BAS - Revision history

>Darklight: /* STOS source code format */

2017-01-20T05:48:23Z

STOS source code format

← Older revision		Revision as of 01:48, 20 January 2017
Line 60:		Line 60:
	\| 0xA0<br>0xB8<br><br> \|\| Extended instruction<br>Extended function \|\| 1 byte: token (0xA0 or 0xB8)<br>1 byte: another token, to lookup in either the extended instructions table or extended functions [[STOS LOOKUP TABLES\|lookup table]]<br>Note: These are nothing to do with extensions, and I guess were added when the programmers realised the wouldnâ€™t fit all the instructions into values 0x80 - 0xFF?		\| 0xA0<br>0xB8<br><br> \|\| Extended instruction<br>Extended function \|\| 1 byte: token (0xA0 or 0xB8)<br>1 byte: another token, to lookup in either the extended instructions table or extended functions [[STOS LOOKUP TABLES\|lookup table]]<br>Note: These are nothing to do with extensions, and I guess were added when the programmers realised the wouldnâ€™t fit all the instructions into values 0x80 - 0xFF?
	\|-		\|-
	\| 0xFA<br><br><br><br><br> \|\| Variable name<br><br><br><br><br> \|\| 1 byte: token (0xFA)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>1 byte: ~~first 3 bits unknown purpose~~, remaining 5 bits, length of variable name<br>3 bytes: unknown purpose<br>''x'' bytes: ASCII variable name, including any '$' or '#' postfix.		\| 0xFA<br><br><br><br><br> \|\| Variable name<br><br><br><br><br> \|\| 1 byte: token (0xFA)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>1 byte: 1st bit set if var is a string, 2nd bit if var is a float, 3rd bit set if var is an array, remaining 5 bits, length of variable name<br>3 bytes: unknown purpose<br>''x'' bytes: ASCII variable name, including any '$' or '#' postfix.
	\|-		\|-
	\| 0xFB<br> \|\| Integer (binary) \|\| ?		\| 0xFB<br> \|\| Integer (binary) \|\| ?

>Wongck at 12:01, 11 October 2011

2011-10-11T12:01:49Z

← Older revision		Revision as of 08:01, 11 October 2011
Line 79:		Line 79:

	[[Category:STOS BASIC]]		[[Category:STOS BASIC]]
			[[Category:Data Formats]]

>Tompee at 13:37, 1 November 2008

2008-11-01T13:37:07Z

← Older revision		Revision as of 09:37, 1 November 2008
Line 1:		Line 1:

	== STOS .BAS file structure ==		== STOS .BAS file structure ==

Line 78:		Line 77:

	--[[User:Darklight\|Darklight]] 20:54, 2 September 2007 (EDT)		--[[User:Darklight\|Darklight]] 20:54, 2 September 2007 (EDT)

			[[Category:STOS BASIC]]

>Lp: /* STOS source code format */

2007-09-13T17:23:40Z

STOS source code format

← Older revision		Revision as of 13:23, 13 September 2007
Line 62:		Line 62:
	\|-		\|-
	\| 0xFA<br><br><br><br><br> \|\| Variable name<br><br><br><br><br> \|\| 1 byte: token (0xFA)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>1 byte: first 3 bits unknown purpose, remaining 5 bits, length of variable name<br>3 bytes: unknown purpose<br>''x'' bytes: ASCII variable name, including any '$' or '#' postfix.		\| 0xFA<br><br><br><br><br> \|\| Variable name<br><br><br><br><br> \|\| 1 byte: token (0xFA)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>1 byte: first 3 bits unknown purpose, remaining 5 bits, length of variable name<br>3 bytes: unknown purpose<br>''x'' bytes: ASCII variable name, including any '$' or '#' postfix.
			\|-
			\| 0xFB<br> \|\| Integer (binary) \|\| ?
	\|-		\|-
	\| 0xFC<br><br><br><br><br> \|\| String literal<br><br><br><br><br> \|\| 1 byte: token (0xFC)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>2 bytes: unknown purpose<br>1 word: string length<br>''x'' bytes: ASCII string value		\| 0xFC<br><br><br><br><br> \|\| String literal<br><br><br><br><br> \|\| 1 byte: token (0xFC)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>2 bytes: unknown purpose<br>1 word: string length<br>''x'' bytes: ASCII string value
			\|-
			\| 0xFD<br> \|\| Integer (hexadecimal) \|\| ?
	\|-		\|-
	\| 0xFE<br><br><br> \|\| Integer<br><br><br> \|\| 1 byte: token (0xFE)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>1 word: integer value		\| 0xFE<br><br><br> \|\| Integer<br><br><br> \|\| 1 byte: token (0xFE)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>1 word: integer value

>Lp: /* STOS source code format */

2007-09-13T17:11:14Z

STOS source code format

← Older revision		Revision as of 13:11, 13 September 2007
Line 67:		Line 67:
	\| 0xFE<br><br><br> \|\| Integer<br><br><br> \|\| 1 byte: token (0xFE)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>1 word: integer value		\| 0xFE<br><br><br> \|\| Integer<br><br><br> \|\| 1 byte: token (0xFE)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>1 word: integer value
	\|-		\|-
	\| 0xFF<br><br><br><br><br> \|\| Floating point number<br><br><br><br> \|\| 1 byte: token (0xFE)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>1 word: number value - 1st 24 bits are the mantissa, 25th bit is the sign, last 7 bits are the exponent<br>4 bytes: unknown purpose<br>Note: to convert to a readable format, each bit of the mantissa = 2 ^ (bit_position + exponent - 88.0). Add up the values indicated by each bit in the mantissa.		\| 0xFF<br><br><br><br><br> \|\| Floating point number<br><br><br><br> \|\| 1 byte: token (0xFE)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>1 word: number value - 1st 24 bits are the mantissa, 25th bit is the sign, last 7 bits are the exponent<br>4 bytes: unknown purpose<br>Note: to convert to a readable format, each bit of the mantissa = 2 ^ (bit_position + exponent - 88.0). Add up the values indicated by each bit in the mantissa. Accurate to 5 decimal places.
	\|-		\|-
	\|}		\|}

>Lp: /* STOS .BAS file structure */

2007-09-11T06:48:00Z

STOS .BAS file structure

← Older revision		Revision as of 02:48, 11 September 2007
Line 7:		Line 7:
	10 bytes Magic "Lionpoulos": STOS basic source		10 bytes Magic "Lionpoulos": STOS basic source
	1 long length of source excluding the header		1 long length of source excluding the header
	1 long offset to first memory bank ~~form~~ end of header		1 long offset to first memory bank from end of header
	15 x		15 x
	{		{
Line 19:		Line 19:
	</pre>		</pre>
	--[[User:Nyh\|Nyh]] 16:18, 10 July 2007 (EDT)		--[[User:Nyh\|Nyh]] 16:18, 10 July 2007 (EDT)




	== STOS source code format ==		== STOS source code format ==

>Darklight: /* STOS source code format */

2007-09-03T02:41:04Z

STOS source code format

← Older revision		Revision as of 22:41, 2 September 2007
Line 44:		Line 44:
	The last line in the source code is always 4 0x00 bytes.		The last line in the source code is always 4 0x00 bytes.

	Most tokens are one byte, and represents one command or function. To find the name of the command or function, look up the byte value in the [[STOS LOOKUP TABLES\|lookup table]].		Most tokens are one byte, and represents one command or function. To find the name of the command or function, look up the byte value in the [[STOS LOOKUP TABLES\|lookup table]].<br>
	Token bytes start from 0x80 onwards. If the token value is 0x7F, use its ascii value.		Token bytes start from 0x80 onwards. If the token value <= 0x7F, use its ascii value. <br>
	There are some special tokens, that may take up more than one byte:		There are some special tokens, that may take up more than one byte:

>Darklight: /* STOS source code format */

2007-09-03T01:47:53Z

STOS source code format

← Older revision		Revision as of 21:47, 2 September 2007
Line 44:		Line 44:
	The last line in the source code is always 4 0x00 bytes.		The last line in the source code is always 4 0x00 bytes.

	Most tokens are one byte, and represents one command or function. To find the name of the command or function, look up the byte value in the lookup table.		Most tokens are one byte, and represents one command or function. To find the name of the command or function, look up the byte value in the [[STOS LOOKUP TABLES\|lookup table]].
	Token bytes start from 0x80 onwards. If the token value is 0x7F, use its ascii value.		Token bytes start from 0x80 onwards. If the token value is 0x7F, use its ascii value.
	There are some special tokens, that may take up more than one byte:		There are some special tokens, that may take up more than one byte:
Line 58:		Line 58:
	\| 0x8A<br><br><br> \|\| Rem or '<br><br><br> \|\| 1 byte: token (0x8A)<br>1 byte: unknown purpose<br>''x'' bytes: ASCII text, terminated by 0x00 end of line token		\| 0x8A<br><br><br> \|\| Rem or '<br><br><br> \|\| 1 byte: token (0x8A)<br>1 byte: unknown purpose<br>''x'' bytes: ASCII text, terminated by 0x00 end of line token
	\|-		\|-
	\| 0xA8<br>0xC0<br><br><br><br><br> \|\| Extension instruction<br>Extension function<br><br><br><br> \|\| 1 byte: token (0xA8 or 0xC0)<br>1 byte: extension index - extension A = 0x00, B = 0x01, â€¦ Z = 0x19<br>1 byte: lookup token - look this value up in the [[STOS.LOOKUP\|extensions lookup table]]<br>Note: The extension index is relevant to the extension configuration at the time of saving the .BAS file. So for a .BAS file that contains extension commands to be correctly interpreted when loading, the same extensions need to be present at the same letters.<br><br>		\| 0xA8<br>0xC0<br><br><br><br><br> \|\| Extension instruction<br>Extension function<br><br><br><br> \|\| 1 byte: token (0xA8 or 0xC0)<br>1 byte: extension index - extension A = 0x00, B = 0x01, â€¦ Z = 0x19<br>1 byte: lookup token - look this value up in the [[STOS LOOKUP TABLES\|extensions lookup table]]<br>Note: The extension index is relevant to the extension configuration at the time of saving the .BAS file. So for a .BAS file that contains extension commands to be correctly interpreted when loading, the same extensions need to be present at the same letters.<br><br>
	\|-		\|-
	\| 0x98<br>0x99<br>0x9A<br>0x9B<br>0x9C<br>0x9D<br>0x9E<br>0x9F \|\| Goto<br>Gosub<br>Then<br>Else<br>Restore<br>For<br>While<br>Repeat \|\| 1 byte: token (0x98, 0x99, â€¦ 0x9F)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>4 bytes: unknown purpose<br><br><br><br><br><br>		\| 0x98<br>0x99<br>0x9A<br>0x9B<br>0x9C<br>0x9D<br>0x9E<br>0x9F \|\| Goto<br>Gosub<br>Then<br>Else<br>Restore<br>For<br>While<br>Repeat \|\| 1 byte: token (0x98, 0x99, â€¦ 0x9F)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>4 bytes: unknown purpose<br><br><br><br><br><br>
	\|-		\|-
	\| 0xA0<br>0xB8<br><br> \|\| Extended instruction<br>Extended function \|\| 1 byte: token (0xA0 or 0xB8)<br>1 byte: another token, to lookup in either the extended instructions table or extended functions table<br>Note: These are nothing to do with extensions, and I guess were added when the programmers realised the wouldnâ€™t fit all the instructions into values 0x80 - 0xFF?		\| 0xA0<br>0xB8<br><br> \|\| Extended instruction<br>Extended function \|\| 1 byte: token (0xA0 or 0xB8)<br>1 byte: another token, to lookup in either the extended instructions table or extended functions [[STOS LOOKUP TABLES\|lookup table]]<br>Note: These are nothing to do with extensions, and I guess were added when the programmers realised the wouldnâ€™t fit all the instructions into values 0x80 - 0xFF?
	\|-		\|-
	\| 0xFA<br><br><br><br><br> \|\| Variable name<br><br><br><br><br> \|\| 1 byte: token (0xFA)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>1 byte: first 3 bits unknown purpose, remaining 5 bits, length of variable name<br>3 bytes: unknown purpose<br>''x'' bytes: ASCII variable name, including any '$' or '#' postfix.		\| 0xFA<br><br><br><br><br> \|\| Variable name<br><br><br><br><br> \|\| 1 byte: token (0xFA)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>1 byte: first 3 bits unknown purpose, remaining 5 bits, length of variable name<br>3 bytes: unknown purpose<br>''x'' bytes: ASCII variable name, including any '$' or '#' postfix.

>Darklight: /* STOS source code format */

2007-09-03T01:45:10Z

STOS source code format

← Older revision		Revision as of 21:45, 2 September 2007
Line 58:		Line 58:
	\| 0x8A<br><br><br> \|\| Rem or '<br><br><br> \|\| 1 byte: token (0x8A)<br>1 byte: unknown purpose<br>''x'' bytes: ASCII text, terminated by 0x00 end of line token		\| 0x8A<br><br><br> \|\| Rem or '<br><br><br> \|\| 1 byte: token (0x8A)<br>1 byte: unknown purpose<br>''x'' bytes: ASCII text, terminated by 0x00 end of line token
	\|-		\|-
	\| 0xA8<br>0xC0<br><br><br><br><br> \|\| Extension instruction<br>Extension function<br><br><br><br> \|\| 1 byte: token (0xA8 or 0xC0)<br>1 byte: extension index - extension A = 0x00, B = 0x01, â€¦ Z = 0x19<br>1 byte: lookup token - look this value up in the extensions lookup table<br>Note: The extension index is relevant to the extension configuration at the time of saving the .BAS file. So for a .BAS file that contains extension commands to be correctly interpreted when loading, the same extensions need to be present at the same letters.<br><br>		\| 0xA8<br>0xC0<br><br><br><br><br> \|\| Extension instruction<br>Extension function<br><br><br><br> \|\| 1 byte: token (0xA8 or 0xC0)<br>1 byte: extension index - extension A = 0x00, B = 0x01, â€¦ Z = 0x19<br>1 byte: lookup token - look this value up in the [[STOS.LOOKUP\|extensions lookup table]]<br>Note: The extension index is relevant to the extension configuration at the time of saving the .BAS file. So for a .BAS file that contains extension commands to be correctly interpreted when loading, the same extensions need to be present at the same letters.<br><br>
	\|-		\|-
	\| 0x98<br>0x99<br>0x9A<br>0x9B<br>0x9C<br>0x9D<br>0x9E<br>0x9F \|\| Goto<br>Gosub<br>Then<br>Else<br>Restore<br>For<br>While<br>Repeat \|\| 1 byte: token (0x98, 0x99, â€¦ 0x9F)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>4 bytes: unknown purpose<br><br><br><br><br><br>		\| 0x98<br>0x99<br>0x9A<br>0x9B<br>0x9C<br>0x9D<br>0x9E<br>0x9F \|\| Goto<br>Gosub<br>Then<br>Else<br>Restore<br>For<br>While<br>Repeat \|\| 1 byte: token (0x98, 0x99, â€¦ 0x9F)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>4 bytes: unknown purpose<br><br><br><br><br><br>

>Darklight: /* STOS source code format */

2007-09-03T01:33:20Z

STOS source code format

← Older revision		Revision as of 21:33, 2 September 2007
Line 39:		Line 39:
	\|-		\|-
	\| x bytes \|\| Tokenized code (length: line length - 4)		\| x bytes \|\| Tokenized code (length: line length - 4)

	\|-		\|-
	\|}<br><br>		\|}<br><br>

			The last line in the source code is always 4 0x00 bytes.

	Most tokens are one byte, and represents one command or function. To find the name of the command or function, look up the byte value in the lookup table.		Most tokens are one byte, and represents one command or function. To find the name of the command or function, look up the byte value in the lookup table.
Line 63:		Line 64:
	\| 0xA0<br>0xB8<br><br> \|\| Extended instruction<br>Extended function \|\| 1 byte: token (0xA0 or 0xB8)<br>1 byte: another token, to lookup in either the extended instructions table or extended functions table<br>Note: These are nothing to do with extensions, and I guess were added when the programmers realised the wouldnâ€™t fit all the instructions into values 0x80 - 0xFF?		\| 0xA0<br>0xB8<br><br> \|\| Extended instruction<br>Extended function \|\| 1 byte: token (0xA0 or 0xB8)<br>1 byte: another token, to lookup in either the extended instructions table or extended functions table<br>Note: These are nothing to do with extensions, and I guess were added when the programmers realised the wouldnâ€™t fit all the instructions into values 0x80 - 0xFF?
	\|-		\|-
	\| 0xFA<br><br><br><br><br> \|\| Variable name<br><br><br><br><br> \|\| 1 byte: token (0xFA)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>1 byte: first 3 bits unknown purpose, remaining 5 bits, length of variable name<br>3 bytes: unknown purpose<br>''x'' bytes: ASCII variable name		\| 0xFA<br><br><br><br><br> \|\| Variable name<br><br><br><br><br> \|\| 1 byte: token (0xFA)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>1 byte: first 3 bits unknown purpose, remaining 5 bits, length of variable name<br>3 bytes: unknown purpose<br>''x'' bytes: ASCII variable name, including any '$' or '#' postfix.
	\|-		\|-
	\| 0xFC<br><br><br><br><br> \|\| String literal<br><br><br><br><br> \|\| 1 byte: token (0xFC)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>2 bytes: unknown purpose<br>1 word: string length<br>''x'' bytes: ASCII string value		\| 0xFC<br><br><br><br><br> \|\| String literal<br><br><br><br><br> \|\| 1 byte: token (0xFC)<br>0 or 1 byte: padding to make the next byte appear at an even position<br>2 bytes: unknown purpose<br>1 word: string length<br>''x'' bytes: ASCII string value