SuperBASIC - Revision history

Agurtovoy: /* Using procedures */

2026-04-27T14:58:26Z

Using procedures

← Older revision		Revision as of 10:58, 27 April 2026
Line 37:		Line 37:
	===== Using procedures =====		===== Using procedures =====

	* The <code>proc</code> keyword is only valid if it appears after an <code>end</code> statement.
	* When calling a procedure use the procedure name followed by parenthesis (), even if the procedure has no parameters.		* When calling a procedure use the procedure name followed by parenthesis (), even if the procedure has no parameters.
	* Avoid any space between the procedure name and the parenthesis, else it will produce an error.		* Avoid any space between the procedure name and the parenthesis, else it will produce an error.

Cibee: Minor formatting changes

2025-09-13T11:44:53Z

Minor formatting changes

← Older revision		Revision as of 07:44, 13 September 2025
Line 174:		Line 174:
	* In place of the <code>memcopy</code> command you would use 3 <code><big>POKEL</big></code> commands and a <code><big>CALL</big></code> command to engage the DMA engine.		* In place of the <code>memcopy</code> command you would use 3 <code><big>POKEL</big></code> commands and a <code><big>CALL</big></code> command to engage the DMA engine.

	~~<code>~~POKEL $0903,data source~~</code>~~		POKEL $0903,data source
	~~<code>~~POKEL $0906,destination~~</code>~~		POKEL $0906,destination
	~~<code>~~POKEL $0909,number of bytes to copy~~</code>~~		POKEL $0909,number of bytes to copy
	~~<code>~~CALL $0900~~</code>~~		CALL $0900

	* [https://github.com/mcassera/F256-mlcopy mlcopy github page]		* [https://github.com/mcassera/F256-mlcopy mlcopy github page]
Line 192:		Line 192:
	SPRITE 3 IMAGE 3 TO 16,16: REM "32x32 Sprite"		SPRITE 3 IMAGE 3 TO 16,16: REM "32x32 Sprite"
	Also, please note that you need to use the command <code>SPRITE X IMAGE Y</code> before setting the sprite coordinates or else BASIC will not know what size is the sprite, and will misalign it, for example the following code although it seems correct will misalign the sprite:		Also, please note that you need to use the command <code>SPRITE X IMAGE Y</code> before setting the sprite coordinates or else BASIC will not know what size is the sprite, and will misalign it, for example the following code although it seems correct will misalign the sprite:
	SPRITE 1 TO 8,8~~<BR>~~		SPRITE 1 TO 8,8
	SPRITE 1 IMAGE 1: REM "USe a 16x16 Sprite"~~<BR>~~		SPRITE 1 IMAGE 1: REM "USe a 16x16 Sprite"

Cibee: Reformatted code sections

2025-09-13T11:42:58Z

Reformatted code sections

← Older revision		Revision as of 07:42, 13 September 2025
Line 12:		Line 12:
	====== Source of this tip: Ernesto ======		====== Source of this tip: Ernesto ======
	* A regular <code>if then</code> condition can't contain an <code>else</code> statement, as in this example:		* A regular <code>if then</code> condition can't contain an <code>else</code> statement, as in this example:
	~~<code>~~10 if a=0 then x=10~~</code>~~		10 if a=0 then x=10
	* If you need to do an <code>if then else</code> structure, you actually have to do an <code>if else endif</code> structure like in the following example, skipping the <code>then</code> statement.		* If you need to do an <code>if then else</code> structure, you actually have to do an <code>if else endif</code> structure like in the following example, skipping the <code>then</code> statement.
	~~<code>~~10 if a=0~~<br />~~		10 if a=0
	20 x=1~~<br />~~		20 x=1
	30 else~~<br />~~		30 else
	40 x=2~~<br />~~		40 x=2
	50 endif~~</code>~~		50 endif
	* If you do it in one line it needs to have some colons added, making it look weird like this:		* If you do it in one line it needs to have some colons added, making it look weird like this:
	~~<code>~~10 if a=0:x=1:else:x=2:endif~~</code>~~		10 if a=0:x=1:else:x=2:endif
	* if you dare to omit the <code>endif</code> thinking that the <code>if</code> statement won't need it, (mmm.., everything is in one line, so no need, right?) -Nope...all hell breaks loose!-		* if you dare to omit the <code>endif</code> thinking that the <code>if</code> statement won't need it, (mmm.., everything is in one line, so no need, right?) -Nope...all hell breaks loose!-
	~~<code>~~10 if a=0:x=1:else:x=2: REM "<-- Error, omited the endif"~~</code>~~		10 if a=0:x=1:else:x=2: REM "<-- Error, omited the endif"
	* be careful not to add an extra <code>then</code> statement by mistake to an <code>if else endif</code> structure, if you do -All hell breaks loose again!!-		* be careful not to add an extra <code>then</code> statement by mistake to an <code>if else endif</code> structure, if you do -All hell breaks loose again!!-
	~~<code>~~10 if a=0 then : rem "<-- Error, THEN is not needed!!!" <br />		10 if a=0 then : rem "<-- Error, THEN is not needed!!!" <br />20 x=1 <br />30 else <br />40 x=2 <br />50 endif
	20 x=1 <br />
	30 else <br />
	40 x=2 <br />
	50 endif~~</code>~~

	''Debugging hint: If you encounter an error like "open structure" or "endproc without a proc": do not trust the line number that you are given. The root of the problem is probably in a structure earlier on in the code.''		''Debugging hint: If you encounter an error like "open structure" or "endproc without a proc": do not trust the line number that you are given. The root of the problem is probably in a structure earlier on in the code.''

Line 192:		Line 187:
	===== Sprite Coordinates =====		===== Sprite Coordinates =====
	In BASIC all sprites are centered on the coordinate specified, this might produce some counterintuitive effects when using different size sprites, for example if you want to align the sprite edge with the top left side of the screen you would need different values depending on the sprite size		In BASIC all sprites are centered on the coordinate specified, this might produce some counterintuitive effects when using different size sprites, for example if you want to align the sprite edge with the top left side of the screen you would need different values depending on the sprite size
			SPRITE 0 IMAGE 1 TO 4,4: REM "8x8 Sprite"
	~~<code>~~SPRITE 0 IMAGE 1 TO 4,4: REM "8x8 Sprite"~~</code></BR>~~		SPRITE 1 IMAGE 1 TO 8,8: REM "16x16 Sprite"
	~~<code>~~SPRITE 1 IMAGE 1 TO 8,8: REM "16x16 Sprite"~~</code></BR>~~		SPRITE 2 IMAGE 2 TO 12,12: REM "24x24 Sprite"
	~~<code>~~SPRITE 2 IMAGE 2 TO 12,12: REM "24x24 Sprite"~~</code></BR>~~		SPRITE 3 IMAGE 3 TO 16,16: REM "32x32 Sprite"
	~~<code>~~SPRITE 3 IMAGE 3 TO 16,16: REM "32x32 Sprite"~~</code></BR>~~

	Also, please note that you need to use the command <code>SPRITE X IMAGE Y</code> before setting the sprite coordinates or else BASIC will not know what size is the sprite, and will misalign it, for example the following code although it seems correct will misalign the sprite:		Also, please note that you need to use the command <code>SPRITE X IMAGE Y</code> before setting the sprite coordinates or else BASIC will not know what size is the sprite, and will misalign it, for example the following code although it seems correct will misalign the sprite:
			SPRITE 1 TO 8,8<BR>
	~~<code>~~SPRITE 1 TO 8,8<~~/code></~~BR>		SPRITE 1 IMAGE 1: REM "USe a 16x16 Sprite"<BR>
	~~<code>~~SPRITE 1 IMAGE 1: REM "USe a 16x16 Sprite"<~~/code></~~BR>

Eacontrerasd at 04:44, 15 May 2025

2025-05-15T04:44:49Z

← Older revision		Revision as of 00:44, 15 May 2025
Line 2:		Line 2:
	* [https://github.com/FoenixRetro/f256-superbasic/blob/main/reference/source/f256jr_basic_ref.pdf SuperBASIC Reference Manual].		* [https://github.com/FoenixRetro/f256-superbasic/blob/main/reference/source/f256jr_basic_ref.pdf SuperBASIC Reference Manual].
	* [[SuperBASIC Memory Map]]		* [[SuperBASIC Memory Map]]
	* SuperBASIC Mix Bag of Code Snippets		* SuperBASIC Mix Bag of [[Code Snippets]]
	* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].		* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].
	* Read EMWhite's [https://apps.emwhite.org/shared-files/885/?Foenix-Rising-Issue-18-November-2024.pdf&download=1 Foenix Rising Issue 18] (November 2024) which goes into detail about a few of the gotchas of superbasic.		* Read EMWhite's [https://apps.emwhite.org/shared-files/885/?Foenix-Rising-Issue-18-November-2024.pdf&download=1 Foenix Rising Issue 18] (November 2024) which goes into detail about a few of the gotchas of superbasic.

Eacontrerasd: Added a Code Snippets reference

2025-05-15T04:43:04Z

Added a Code Snippets reference

← Older revision		Revision as of 00:43, 15 May 2025
Line 2:		Line 2:
	* [https://github.com/FoenixRetro/f256-superbasic/blob/main/reference/source/f256jr_basic_ref.pdf SuperBASIC Reference Manual].		* [https://github.com/FoenixRetro/f256-superbasic/blob/main/reference/source/f256jr_basic_ref.pdf SuperBASIC Reference Manual].
	* [[SuperBASIC Memory Map]]		* [[SuperBASIC Memory Map]]
			* SuperBASIC Mix Bag of Code Snippets
	* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].		* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].
	* Read EMWhite's [https://apps.emwhite.org/shared-files/885/?Foenix-Rising-Issue-18-November-2024.pdf&download=1 Foenix Rising Issue 18] (November 2024) which goes into detail about a few of the gotchas of superbasic.		* Read EMWhite's [https://apps.emwhite.org/shared-files/885/?Foenix-Rising-Issue-18-November-2024.pdf&download=1 Foenix Rising Issue 18] (November 2024) which goes into detail about a few of the gotchas of superbasic.

Mcassera: /* Note */

2024-11-27T02:29:09Z

Note

← Older revision		Revision as of 22:29, 26 November 2024
Line 160:		Line 160:
	\|15		\|15
	\|White		\|White
	\|}		\|}The background colors do not work when the bitmap layer has been turned on. They will also not work if you have returned from the bitmap layer with a <code>bitmap off</code> command. In order to restore the background control character function you will need to make sure the MMU is set to zero by using <code>POKE 1,0</code> and then setting the text mode again by using <code>POKE $d000,1</code>.

	~~==== '''<u>Note</u>''' ====~~
	The background colors do not work when the bitmap layer has been turned on. They will also not work if you have returned from the bitmap layer with a <code>bitmap off</code> command. In order to restore the background control character function you will need to make sure the MMU is set to zero by using <code>POKE 1,0</code> and then setting the text mode again by using <code>POKE $d000,1</code>.

	==== Character Set / Text matrix ====		==== Character Set / Text matrix ====

Mcassera: /* Note */

2024-11-27T02:27:36Z

Note

← Older revision		Revision as of 22:27, 26 November 2024
Line 163:		Line 163:

	==== '''<u>Note</u>''' ====		==== '''<u>Note</u>''' ====
	The background colors do not work when the bitmap layer has been turned on. They will also not work if you have returned from the bitmap layer with a bitmap off command. In order to restore the background control character function you will need to make sure the MMU is set to zero by using POKE 1,0 and then setting the text mode again by using POKE $d000,1.		The background colors do not work when the bitmap layer has been turned on. They will also not work if you have returned from the bitmap layer with a <code>bitmap off</code> command. In order to restore the background control character function you will need to make sure the MMU is set to zero by using <code>POKE 1,0</code> and then setting the text mode again by using <code>POKE $d000,1</code>.

	==== Character Set / Text matrix ====		==== Character Set / Text matrix ====

Mcassera: /* Note */

2024-11-27T02:24:37Z

Note

← Older revision		Revision as of 22:24, 26 November 2024
Line 162:		Line 162:
	\|}		\|}

	=== '''<u>Note</u>''' ===		==== '''<u>Note</u>''' ====
	The background colors do not work when the bitmap layer has been turned on. They will also not work if you have returned from the bitmap layer with a bitmap off command. In order to restore the background control character function you will need to make sure the MMU is set to zero by using POKE 1,0 and then setting the text mode again by using POKE $d000,1.		The background colors do not work when the bitmap layer has been turned on. They will also not work if you have returned from the bitmap layer with a bitmap off command. In order to restore the background control character function you will need to make sure the MMU is set to zero by using POKE 1,0 and then setting the text mode again by using POKE $d000,1.

	===== Character Set / Text matrix =====		==== Character Set / Text matrix ====

	* Access to the full character set can be obtained by using the <code>CPRINT</code> command instead of the normal <code>PRINT</code> command.		* Access to the full character set can be obtained by using the <code>CPRINT</code> command instead of the normal <code>PRINT</code> command.
	* Characters can also be set on the screen text matrix using the <code>POKE</code> command starting at <code>$C000</code> providing the MMU I/O control is set to 2 by executing a <code>POKE 1,2</code> command first (remember to restore the MMU I/O once you're done).		* Characters can also be set on the screen text matrix using the <code>POKE</code> command starting at <code>$C000</code> providing the MMU I/O control is set to 2 by executing a <code>POKE 1,2</code> command first (remember to restore the MMU I/O once you're done).

Mcassera: /* Control characters for cursor and colour control */

2024-11-27T02:24:08Z

Control characters for cursor and colour control

← Older revision		Revision as of 22:24, 26 November 2024
Line 161:		Line 161:
	\|White		\|White
	\|}		\|}

			=== '''<u>Note</u>''' ===
			The background colors do not work when the bitmap layer has been turned on. They will also not work if you have returned from the bitmap layer with a bitmap off command. In order to restore the background control character function you will need to make sure the MMU is set to zero by using POKE 1,0 and then setting the text mode again by using POKE $d000,1.

	===== Character Set / Text matrix =====		===== Character Set / Text matrix =====

1BitFeverDreams: attempt to make the link at least work despite the security warning

2024-11-18T03:11:10Z

attempt to make the link at least work despite the security warning

← Older revision		Revision as of 23:11, 17 November 2024
Line 3:		Line 3:
	* [[SuperBASIC Memory Map]]		* [[SuperBASIC Memory Map]]
	* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].		* Watch EMWhite's excellent intro series on YouTube: [https://www.youtube.com/playlist?list=PLeHjTvk7NPiSqGz4REMH-S4hjYpLS2YNR Full Playlist].
	* Read EMWhite's [~~http~~://apps.emwhite.org/shared-files/885/?Foenix-Rising-Issue-18-November-2024.pdf&download=1 Foenix Rising Issue 18] (November 2024) which goes into detail about a few of the gotchas of superbasic.		* Read EMWhite's [https://apps.emwhite.org/shared-files/885/?Foenix-Rising-Issue-18-November-2024.pdf&download=1 Foenix Rising Issue 18] (November 2024) which goes into detail about a few of the gotchas of superbasic.

	=== An informal list of tips, "gotchas": ===		=== An informal list of tips, "gotchas": ===