STOS BASIC COMPILER INSTRUCTIONS - Revision history

>Stnoob: /* PASS 2 */ removed carriage return

2016-02-15T10:26:39Z

PASS 2: removed carriage return

← Older revision		Revision as of 06:26, 15 February 2016
Line 474:		Line 474:

	==== PASS 2 ====		==== PASS 2 ====
	This pass simply explores the relocation table created in pass 1, and sets the required addresses in the compiled program. The compiler now closes all the open disc files, and transfers the program to the current program segment if required. Note that the eventual size of a compiled program depends entirely on the precise mix of STOS instructions which are used. there's no real relationship between the complexity of the program and the size of the code. In practice, some of the simplest Basic instructions proved to be the hardest to actually write. A good example of this is the STOS file selector, which involves over 4k of machine code. You can see below the machine code produced by		This pass simply explores the relocation table created in pass 1, and sets the required addresses in the compiled program. The compiler now closes all the open disc files, and transfers the program to the current program segment if required. Note that the eventual size of a compiled program depends entirely on the precise mix of STOS instructions which are used. there's no real relationship between the complexity of the program and the size of the code. In practice, some of the simplest Basic instructions proved to be the hardest to actually write. A good example of this is the STOS file selector, which involves over 4k of machine code. You can see below the machine code produced by the compiler from a simple plot command.
	the compiler from a simple plot command.
	The basic listing:		The basic listing:
	<pre>		<pre>

>Stnoob: /* THE NEW FLOATING POINT ROUTINES. */ fixed layout

2016-02-15T10:26:01Z

THE NEW FLOATING POINT ROUTINES.: fixed layout

← Older revision		Revision as of 06:26, 15 February 2016
Line 410:		Line 410:
	Incidentally, if you try to list any of your existing programs which use real numbers, the following text will be displayed on the screen.		Incidentally, if you try to list any of your existing programs which use real numbers, the following text will be displayed on the screen.
	<pre>		<pre>
	BAD FLOAT TRAP		BAD FLOAT TRAP
	</pre>		</pre>
	In order to allow you to run these programs from STOS v2.4 we have included a useful little utility called CONVERT.BAS which will automatically transform your programs into the correct format.		In order to allow you to run these programs from STOS v2.4 we have included a useful little utility called CONVERT.BAS which will automatically transform your programs into the correct format.
Line 416:		Line 416:
	You can call this program from the compiler disc by typing:		You can call this program from the compiler disc by typing:
	<pre>		<pre>
	RUN "CONVERT.BAS"		RUN "CONVERT.BAS"
	</pre>		</pre>
	You will now be prompted for one of your STOS V2.3 programs. Insert the appropriate disc in drive A and select your program using the STOS file selector. This program will then be quickly converted into STOS V2.4 format, and will be copied back to the original file. It's a good idea to perform this conversion process for every one of your STOS Basic programs which use real numbers. This will avoid the risk of confusion in the future.		You will now be prompted for one of your STOS V2.3 programs. Insert the appropriate disc in drive A and select your program using the STOS file selector. This program will then be quickly converted into STOS V2.4 format, and will be copied back to the original file. It's a good idea to perform this conversion process for every one of your STOS Basic programs which use real numbers. This will avoid the risk of confusion in the future.

>Stnoob: /* THE COMPILER GENERATES AN OUT OF MEMORY ERROR */ fixed layout (missed a line last time)

2016-02-15T10:25:25Z

THE COMPILER GENERATES AN OUT OF MEMORY ERROR: fixed layout (missed a line last time)

← Older revision		Revision as of 06:25, 15 February 2016
Line 297:		Line 297:

	MEMORY DISC SLIGHTLY SLOWER THAN DISC TO MEMORY BUT THE		MEMORY DISC SLIGHTLY SLOWER THAN DISC TO MEMORY BUT THE
	MEMORY USAGE CAN OCCASIONALLY BE LESS.		MEMORY USAGE CAN OCCASIONALLY BE LESS.

	DISC DISC USES VERY LITTLE MEMORY.		DISC DISC USES VERY LITTLE MEMORY.

>Stnoob: /* THE COMPILER GENERATES AN OUT OF MEMORY ERROR */ fixed layout

2016-02-15T10:24:57Z

THE COMPILER GENERATES AN OUT OF MEMORY ERROR: fixed layout

← Older revision		Revision as of 06:24, 15 February 2016
Line 290:		Line 290:
	This can happen if you are trying to compile a large (100k+) program on an unexpanded 520 ST. the compiler provides you with four different options which can be used to conserve memory. Here is a list of the various possibilities in descending order of speed:		This can happen if you are trying to compile a large (100k+) program on an unexpanded 520 ST. the compiler provides you with four different options which can be used to conserve memory. Here is a list of the various possibilities in descending order of speed:
	<pre>		<pre>
	SOURCE DESTINATION COMMENTS		SOURCE DESTINATION COMMENTS

	MEMORY MEMORY VERY FAST - USES MAXIMUM AMOUNT OF MEMORY.		MEMORY MEMORY VERY FAST - USES MAXIMUM AMOUNT OF MEMORY.

	DISC MEMORY SLOWER BUT USES CONSIDERABLY LESS MEMORY.		DISC MEMORY SLOWER BUT USES CONSIDERABLY LESS MEMORY.

	MEMORY DISC SLIGHTLY SLOWER THAN DISC TO MEMORY BUT THE		MEMORY DISC SLIGHTLY SLOWER THAN DISC TO MEMORY BUT THE
	MEMORY USAGE CAN OCCASIONALLY BE LESS.		MEMORY USAGE CAN OCCASIONALLY BE LESS.

	DISC DISC USES VERY LITTLE MEMORY.		DISC DISC USES VERY LITTLE MEMORY.
	</pre>		</pre>
	The only limit to the size of your programs is the amount of available disc space. This is quite slow on a single floppy. When you get an out of memory error, you should try each of the above options in turn. If you still get an out of memory error, you will need to reduce the size of your program in some way. The easiest solution is to get rid of the permanent memory banks which are used by the program. These can be defined during program initialization using the RESERVE command and loaded separately from the disc. Your programs initialization phase will now include the following steps.		The only limit to the size of your programs is the amount of available disc space. This is quite slow on a single floppy. When you get an out of memory error, you should try each of the above options in turn. If you still get an out of memory error, you will need to reduce the size of your program in some way. The easiest solution is to get rid of the permanent memory banks which are used by the program. These can be defined during program initialization using the RESERVE command and loaded separately from the disc. Your programs initialization phase will now include the following steps.

>Stnoob: /* COMPILER TUTORIAL */ fixed layout

2016-02-15T10:24:27Z

COMPILER TUTORIAL: fixed layout

← Older revision		Revision as of 06:24, 15 February 2016
Line 222:		Line 222:
	Now enter the following STOS program into your computer:		Now enter the following STOS program into your computer:
	<pre>		<pre>
	10 TIMER=0:FOR I=1 TO 100000:NEXT I		10 TIMER=0:FOR I=1 TO 100000:NEXT I
	20 PRINT "LOOP TOOK "; TIMER / 50!; " SECONDS"		20 PRINT "LOOP TOOK "; TIMER / 50!; " SECONDS"
	</pre>		</pre>
	This program will take approximately seven seconds to run using interpreted STOS Basic. Insert a disc containing the compiler folder in drive A, and enter the accessory menu with the <HELP> key. The compiler can now be accessed by selecting the COMPILER accessory. Move the pointer over the COMPILE button and click on the mouse. The disc will now whir for a few seconds as the required compiler libraries are accessed from the disc. As the program is translated, the progress of the compiler is represented by a horizontal bar. When this reaches the edge of the screen, the compilation process has been successfully completed. You will now be presented with the option to grab your finished program into one of the available program segments.		This program will take approximately seven seconds to run using interpreted STOS Basic. Insert a disc containing the compiler folder in drive A, and enter the accessory menu with the <HELP> key. The compiler can now be accessed by selecting the COMPILER accessory. Move the pointer over the COMPILE button and click on the mouse. The disc will now whir for a few seconds as the required compiler libraries are accessed from the disc. As the program is translated, the progress of the compiler is represented by a horizontal bar. When this reaches the edge of the screen, the compilation process has been successfully completed. You will now be presented with the option to grab your finished program into one of the available program segments.
Line 230:		Line 230:
	Incidentally, since the program has been converted into machine code, any attempt to generate a listing will produce the response:		Incidentally, since the program has been converted into machine code, any attempt to generate a listing will produce the response:
	<pre>		<pre>
	******************************		******************************
	* COMPILED PROGRAM *		* COMPILED PROGRAM *
	* Don't change line 65535! *		* Don't change line 65535! *
	******************************		******************************
	</pre>		</pre>
	Line 65535 contains a special instruction which executes the compiled program stored in the ST's memory. Removing this line will effectively destroy your compiled program. It's theoretically possible to incorporate separate lines of interpreted Basic into the compiled program. This practice is NOT however, recommended. Note that compiled programs can also be accessed using the normal LOAD and SAVE instructions, if you wanted to save you current program, you could therefore type something like:		Line 65535 contains a special instruction which executes the compiled program stored in the ST's memory. Removing this line will effectively destroy your compiled program. It's theoretically possible to incorporate separate lines of interpreted Basic into the compiled program. This practice is NOT however, recommended. Note that compiled programs can also be accessed using the normal LOAD and SAVE instructions, if you wanted to save you current program, you could therefore type something like:

>Stnoob: /* AUTO-LOADING THE COMPILER */ fixed layout and added spaces where needed.

2016-02-15T10:23:24Z

AUTO-LOADING THE COMPILER: fixed layout and added spaces where needed.

← Older revision		Revision as of 06:23, 15 February 2016
Line 65:		Line 65:

	=== AUTO-LOADING THE COMPILER ===		=== AUTO-LOADING THE COMPILER ===
	The action of the compiler is controlled through the accessory program COMPILER.ACB. This can be loaded automatically by changing the the EDITOR.ENV file on the STOS boot disc. Insert the original STOS language disc into drive A and run the configuration program CONFIG by typing: RUN"CONFIG.BAS" When the main menu appears, click on the NEXT PAGE icon. You can now add COMPILER.ACB to the list of accessories which will be loaded on start-up. Click the mouse on the first free space of the accessory list and enter the line: COMPILER.ACB It's a good idea to add the following function key definitions to the standard list. This will simplify the process of loading and saving compiled programs considerably.		The action of the compiler is controlled through the accessory program COMPILER.ACB. This can be loaded automatically by changing the the EDITOR.ENV file on the STOS boot disc. Insert the original STOS language disc into drive A and run the configuration program CONFIG by typing:
	<pre>		<pre>
	F14(shift-F4) fload"*.CMP"		RUN "CONFIG.BAS"
	F15(shift-F5) fsave"*.CMP"		</pre>
			When the main menu appears, click on the NEXT PAGE icon. You can now add COMPILER.ACB to the list of accessories which will be loaded on start-up. Click the mouse on the first free space of the accessory list and enter the line: COMPILER.ACB It's a good idea to add the following function key definitions to the standard list. This will simplify the process of loading and saving compiled programs considerably.
			<pre>
			F14(shift-F4) fload "*.CMP"
			F15(shift-F5) fsave "*.CMP"
	</pre>		</pre>
	You can now save the new configuration file onto your working copy of STOS Basic using the "SAVE ON DISC" command. Then copy the COMPILER.ACB file onto the language disc so that STOS Basic can pick it up off the root directory as it boots up.		You can now save the new configuration file onto your working copy of STOS Basic using the "SAVE ON DISC" command. Then copy the COMPILER.ACB file onto the language disc so that STOS Basic can pick it up off the root directory as it boots up.

>Stnoob: /* A PREVIOUSLY ERROR-FREE PROGRAM RETURNS A SYNTAX ERROR WHEN compiled */ fixed layout

2016-02-15T10:19:16Z

A PREVIOUSLY ERROR-FREE PROGRAM RETURNS A SYNTAX ERROR WHEN compiled: fixed layout

← Older revision		Revision as of 06:19, 15 February 2016
Line 338:		Line 338:

	This happens quite often, and is simply a reflection of the improved sensitivity of the compiler to genuine syntax errors. Take the following program:		This happens quite often, and is simply a reflection of the improved sensitivity of the compiler to genuine syntax errors. Take the following program:
	<pre>		<pre>
	10 print "hi there"		10 print "hi there"
	20 goto 10		20 goto 10

>Stnoob: /* GEM-RUN OPTIONS */ Fixed layout

2016-02-15T10:18:27Z

GEM-RUN OPTIONS: Fixed layout

← Older revision		Revision as of 06:18, 15 February 2016
Line 166:		Line 166:
	The first icons select one of the 16 possible colours to be set (4 in medium resolution).		The first icons select one of the 16 possible colours to be set (4 in medium resolution).
	<pre>		<pre>
	I ++ I CLICK ON THIS BOX TO INCREMENT THE COLOUR BY ONE		I ++ I CLICK ON THIS BOX TO INCREMENT THE COLOUR BY ONE

	I COLOUR I		I COLOUR I

>Stnoob: /* USING THE COMPILER WITH A HARD DISC */ fixed layout

2016-02-15T10:18:02Z

USING THE COMPILER WITH A HARD DISC: fixed layout

← Older revision		Revision as of 06:18, 15 February 2016
Line 103:		Line 103:
	<pre>		<pre>
	load "COMPILER.ACB"		load "COMPILER.ACB"
	10 COMPATH$ = "D:\STOS\UTILITY": REM example path name		10 COMPATH$ = "D:\STOS\UTILITY": REM example path name
	SAVE "COMPILER.ACB"		SAVE "COMPILER.ACB"
	</pre>		</pre>

>Stnoob: /* THE COMPILER RETURNS AN UNDIMENSIONED ARRAY ERROR FOR AN ARRAY WHICH HAS APPARENTLY BEEN CORRECTLY DIMENSIONED. */ fixed layout

2016-02-15T10:14:36Z

THE COMPILER RETURNS AN UNDIMENSIONED ARRAY ERROR FOR AN ARRAY WHICH HAS APPARENTLY BEEN CORRECTLY DIMENSIONED.: fixed layout

← Older revision		Revision as of 06:14, 15 February 2016
Line 317:		Line 317:
	20 A(10)=50		20 A(10)=50
	30 END		30 END
	1000 DIM a(100): RETURN		1000 DIM a(100): RETURN
	</pre>		</pre>
	This causes an error because when the compiler checks line 20, it has yet to encounter the DIM statement at line 1000. It therefore generates an erroneous error message. The solution to this problem is simply to dimension all arrays at the start of the program. So you can fix the above routine by replacing line 10 with:		This causes an error because when the compiler checks line 20, it has yet to encounter the DIM statement at line 1000. It therefore generates an erroneous error message. The solution to this problem is simply to dimension all arrays at the start of the program. So you can fix the above routine by replacing line 10 with:
Line 323:		Line 323:
	10 dim a(100)		10 dim a(100)
	</pre>		</pre>

	=== YOU GET A SYNTAX ERROR AT AN ON...GOTO OR ON...GOSUB STATEMENT ===		=== YOU GET A SYNTAX ERROR AT AN ON...GOTO OR ON...GOSUB STATEMENT ===