The Structure of I-Code - Revision history

Polluks: Category

2015-09-11T17:45:05Z

Wayne: /* DATA Statement Structure */

2013-10-14T14:52:39Z

DATA Statement Structure

← Older revision		Revision as of 10:52, 14 October 2013
Line 588:		Line 588:
	:{\| border="1" cellspacing="0" cellpadding="5"		:{\| border="1" cellspacing="0" cellpadding="5"
	\|-		\|-
	\| colspan="13"\|DATA 9600,4800,2400,1200,300		\| colspan="14"\|DATA 9600,4800,2400,1200,300
	\|-		\|-
	\|~~00000084\|\|04\|\|8E 2580\|\|4B\|\|8E 12C0\|\|4B\|\|8E 0960\|\|4B~~\|\|~~8E 04B0\|\|4B\|\|8E 012C\|\|55 0066~~\|\|3F		\| colspan="4" \|1st DATA statement address:      0066\|\| colspan="10"\|
	\|-		\|-
	\|Mod Off\|\|DATA\|\|9600\|\|,\|\|4800\|\|,\|\|2400\|\|,\|\|1200\|\|,\|\|300\|\|<ivgt>\|\|<eol>		\|00000084\|\|0064\|\|04\|\|8E 2580\|\|4B\|\|8E 12C0\|\|4B\|\|8E 0960\|\|4B\|\|8E 04B0\|\|4B\|\|8E 012C\|\|55 0066\|\|3F
			\|-
			\|Mod Off\|\|Exec Off\|\|DATA\|\|9600\|\|,\|\|4800\|\|,\|\|2400\|\|,\|\|1200\|\|,\|\|300\|\|<ivgt>\|\|<eol>
	\|}		\|}

Wayne: /* DATA Statement Structure */

2013-10-14T14:39:50Z

DATA Statement Structure

← Older revision		Revision as of 10:39, 14 October 2013
Line 585:		Line 585:

	The structure is not doubly-linked, and you can only move through it sequentially in one direction.		The structure is not doubly-linked, and you can only move through it sequentially in one direction.

			:{\| border="1" cellspacing="0" cellpadding="5"
			\|-
			\| colspan="13"\|DATA 9600,4800,2400,1200,300
			\|-
			\|00000084\|\|04\|\|8E 2580\|\|4B\|\|8E 12C0\|\|4B\|\|8E 0960\|\|4B\|\|8E 04B0\|\|4B\|\|8E 012C\|\|55 0066\|\|3F
			\|-
			\|Mod Off\|\|DATA\|\|9600\|\|,\|\|4800\|\|,\|\|2400\|\|,\|\|1200\|\|,\|\|300\|\|<ivgt>\|\|<eol>
			\|}

	==File Access Mode Tokens==		==File Access Mode Tokens==

Wayne: /* DATA Statement Structure */

2013-10-14T14:09:50Z

DATA Statement Structure

← Older revision		Revision as of 10:09, 14 October 2013
Line 574:		Line 574:

	==DATA Statement Structure==		==DATA Statement Structure==
			DATA statements in Basic09 are essentially linked-lists.

			The 1st data statement address field in the module header points to the first byte of the first item in the first DATA statement in the procedure. It does not point to the DATA token.

			At the end of each DATA statement is a invisible goto that points to the first byte of the first item in the next DATA statement, or of the first DATA statement if the current DATA statement is the last DATA statement in the procedure.

			It is the address in the header that allows RESTORE with no line number to reset to the beginning of the DATA statements.

			RESTORE with a line number allows you to insert points within the structure to allow the pointer to be re-positioned.

			The structure is not doubly-linked, and you can only move through it sequentially in one direction.

	==File Access Mode Tokens==		==File Access Mode Tokens==

Wayne: /* About GOTO, GOSUB and tokens */

2013-10-14T14:04:00Z

About GOTO, GOSUB and tokens

← Older revision		Revision as of 10:04, 14 October 2013
Line 572:		Line 572:

	This is why the line number at the beginning of a line can disappear from your I-Code. Without an identifier to point to it, that reference does not exist in packed I-Code.		This is why the line number at the beginning of a line can disappear from your I-Code. Without an identifier to point to it, that reference does not exist in packed I-Code.

			==DATA Statement Structure==

	==File Access Mode Tokens==		==File Access Mode Tokens==

Wayne: /* IF-THEN/ENDIF */

2013-09-18T21:51:12Z

IF-THEN/ENDIF

← Older revision		Revision as of 17:51, 18 September 2013
Line 415:		Line 415:
	\|10\|\|84 01CF\|\|8D 02\|\|C1\|\|90 2D44 FF\|\|DF\|\|55 03DD\|\|45\|\|3E		\|10\|\|84 01CF\|\|8D 02\|\|C1\|\|90 2D44 FF\|\|DF\|\|55 03DD\|\|45\|\|3E
	\|-		\|-
	\|IF\|\|S0098\|\|<bc> 2\|\|LEFT$(,)\|\|"-D"\|\|=\|\|<ivgt>\|\|THEN\|\|~~<eol>~~		\|IF\|\|S0098\|\|<bc> 2\|\|LEFT$(,)\|\|"-D"\|\|=\|\|<ivgt>\|\|THEN\|\|\
	\|}		\|}

Wayne: /* Files */

2013-09-18T21:42:02Z

Files

← Older revision		Revision as of 17:42, 18 September 2013
Line 162:		Line 162:
	File access in Basic09 is accomplished through a specific set of keywords and functions. OPEN and CREATE statements deal with opening or creating a file on your disk. Both statements have the same syntax, and except for the OPEN or CREATE keyword are syntactically identical:		File access in Basic09 is accomplished through a specific set of keywords and functions. OPEN and CREATE statements deal with opening or creating a file on your disk. Both statements have the same syntax, and except for the OPEN or CREATE keyword are syntactically identical:

	{\| border="1" cellspacing="0" cellpadding="5"		:{\| border="1" cellspacing="0" cellpadding="5"
	\|-		\|-
	\| colspan="6"\|CREATE #path,filename		\| colspan="6"\|CREATE #path,filename
Line 172:		Line 172:


	{\| border="1" cellspacing="0" cellpadding="5"		:{\| border="1" cellspacing="0" cellpadding="5"
	\|-		\|-
	\| colspan="8"\|OPEN #path,filename:READ		\| colspan="8"\|OPEN #path,filename:READ
Line 183:		Line 183:
	SEEK #path, SIZE(myVar)		SEEK #path, SIZE(myVar)

	{\| border="1" cellspacing="0" cellpadding="5"		:{\| border="1" cellspacing="0" cellpadding="5"
	\|-		\|-
	\| colspan="4"\|CLOSE #path		\| colspan="4"\|CLOSE #path
Line 193:		Line 193:


	{\| border="1" cellspacing="0" cellpadding="5"		:{\| border="1" cellspacing="0" cellpadding="5"
	\|-		\|-
	\| colspan="3"\|DELETE filename		\| colspan="3"\|DELETE filename

Wayne: /* Files */

2013-09-18T21:40:23Z

Files

← Older revision		Revision as of 17:40, 18 September 2013
Line 162:		Line 162:
	File access in Basic09 is accomplished through a specific set of keywords and functions. OPEN and CREATE statements deal with opening or creating a file on your disk. Both statements have the same syntax, and except for the OPEN or CREATE keyword are syntactically identical:		File access in Basic09 is accomplished through a specific set of keywords and functions. OPEN and CREATE statements deal with opening or creating a file on your disk. Both statements have the same syntax, and except for the OPEN or CREATE keyword are syntactically identical:

	{\| border=1		{\| border="1" cellspacing="0" cellpadding="5"
	\|-		\|-
	\| colspan=7\|CREATE #path,~~"[my/Pathlist/]File"[:MODE]\|~~		\| colspan="6"\|CREATE #path,filename
	\|-		\|-
	\|29\|54\|80 0016\|4B\|84 0000\|3F\|		\|29\|\|54\|\|80 0016\|\|4B\|\|84 0000\|\|3F
	\|-		\|-
	\| ~~colspan=7~~\|~~OPEN~~ #~~path,"[my/Pathlist/]File"[:MODE]~~\|		\|CREATE\|\|#\|\|path\|\|,\|\|filename\|\|<eol>
	\|-
	\|2A\|~~54\|80 0016\|4B~~\|~~84 0000~~\|~~4A 01~~\|3F\|
	\|}		\|}

	* See [[#File Access Mode Tokens\|File Access Mode Tokens]].

	~~SEEK allows you to move the file pointer for the specified file~~ path ~~anywhere within the file~~:		{\| border="1" cellspacing="0" cellpadding="5"
			\|-
			\| colspan="8"\|OPEN #path,filename:READ
			\|-
			\|2A\|\|54\|\|80 0016\|\|4B\|\|84 0000\|\|4A\|\|01\|\|3F
			\|-
			\|OPEN\|\|#\|\|path\|\|,\|\|filename\|\|:\|\|READ\|\|<eol>
			\|}

	SEEK #path, SIZE(myVar)		SEEK #path, SIZE(myVar)

	CLOSE ~~closes the file specified:~~		{\| border="1" cellspacing="0" cellpadding="5"
			\|-
			\| colspan="4"\|CLOSE #path
			\|-
			\|30\|\|54\|\|80 0016\|\|3F
			\|-
			\|CLOSE\|\|#\|\|path\|\|<eol>
			\|}

	~~CLOSE #path[,path1, ... pathN]~~

	DELETE ~~deletes a specified file by name:~~		{\| border="1" cellspacing="0" cellpadding="5"
			\|-
			\| colspan="3"\|DELETE filename
			\|-
			\|32\|\|84 0000\|\|3F
			\|-
			\|DELETE\|\|filename\|\|<eol>
			\|}

	~~DELETE "my/Pathlist/~~File"		* See [[#File Access Mode Tokens\|File Access Mode Tokens]].

	====Data Memory Map====		====Data Memory Map====

Wayne: /* Files */

2013-09-18T21:14:25Z

Files

← Older revision		Revision as of 17:14, 18 September 2013
Line 162:		Line 162:
	File access in Basic09 is accomplished through a specific set of keywords and functions. OPEN and CREATE statements deal with opening or creating a file on your disk. Both statements have the same syntax, and except for the OPEN or CREATE keyword are syntactically identical:		File access in Basic09 is accomplished through a specific set of keywords and functions. OPEN and CREATE statements deal with opening or creating a file on your disk. Both statements have the same syntax, and except for the OPEN or CREATE keyword are syntactically identical:

	~~OPEN~~ #path,"[my/Pathlist/]File"[:MODE]~~<br>~~		{\| border=1
	~~CREATE~~ #path,"[my/Pathlist/]File"[:MODE]		\|-
			\| colspan=7\|CREATE #path,"[my/Pathlist/]File"[:MODE]\|
			\|-
			\|29\|54\|80 0016\|4B\|84 0000\|3F\|
			\|-
			\| colspan=7\|OPEN #path,"[my/Pathlist/]File"[:MODE]\|
			\|-
			\|2A\|54\|80 0016\|4B\|84 0000\|4A 01\|3F\|
			\|}

	* See [[#File Access Mode Tokens\|File Access Mode Tokens]].		* See [[#File Access Mode Tokens\|File Access Mode Tokens]].

Wayne: /* Files */

2013-09-18T20:39:54Z

Files

← Older revision		Revision as of 16:39, 18 September 2013
Line 162:		Line 162:
	File access in Basic09 is accomplished through a specific set of keywords and functions. OPEN and CREATE statements deal with opening or creating a file on your disk. Both statements have the same syntax, and except for the OPEN or CREATE keyword are syntactically identical:		File access in Basic09 is accomplished through a specific set of keywords and functions. OPEN and CREATE statements deal with opening or creating a file on your disk. Both statements have the same syntax, and except for the OPEN or CREATE keyword are syntactically identical:

	OPEN #path,"[my/Pathlist/]File"[:MODE]		OPEN #path,"[my/Pathlist/]File"[:MODE]<br>
	CREATE #path,"[my/Pathlist/]File"[:MODE]		CREATE #path,"[my/Pathlist/]File"[:MODE]

Line 173:		Line 173:
	CLOSE closes the file specified:		CLOSE closes the file specified:

	CLOSE #path		CLOSE #path[,path1, ... pathN]

	DELETE deletes a specified file by name:		DELETE deletes a specified file by name:

← Older revision		Revision as of 13:45, 11 September 2015
Line 2,980:		Line 2,980:
	\|STRING Constant (Literal) - Terminator		\|STRING Constant (Literal) - Terminator
	\|}		\|}

			[[Category:OS-9]]