View source for Technical information about Locomotive BASIC

[[Category:Cpctech.org]]

'''''This article originally came from Kevin Thackers' archive at [http://www.cpctech.org.uk http://www.cpctech.org.uk].''''' 

= Technical information about Locomotive BASIC  =

The are two versions of Locomotive BASIC used in the Amstrad CPC and CPC+ computers. v1.0 is used by the CPC464, and v1.1 is used by the CPC664, CPC6128, CPC464+ and CPC6128+. 

== BASIC v1.0 only ==

There is a region of memory between AC00-AC1B which is filled with RET instructions. The BASIC ROM calls the following locations:
AC01,AC04,AC07,AC0A,AC0D,AC10,AC13,AC16,AC19

It almost looks like these were used for debugging the ROM but were left in.

They can be used to implement new BASIC commands.

== Passing parameters to a RSX (Resident System Extension) command or binary function  ==

A RSX (Resident System Extension) command is accessed through BASIC with a "|" character prefix. e.g. The "DIR" RSX, is accessed by "|DIR".  A binary function is accessed through BASIC using the "CALL" command. 

Both RSX and CALL commands work (are!) similar from the BASIC command line and invoke machine code - the only difference is: with the help of a RSX command you don't need to know the exact access address. You can pass up to 32 parameters with a CALL or RSX command. Possible parameters could be integer, floating points and strings. Just store the parameter into a variable:
Passing for integer:
<pre>
CALL &4000,32,34,&5E,&x10101010
|RSX-command,32,34,&5E,&x10101010
</pre>
Passing for floating points
<pre>
@a!=43.375
CALL or |RSX-command,@a!
</pre>

<br> Passing a string parameter: 
<br> BASIC v1.0 
<pre>a$="A":|DRIVE,@a$
</pre> 
BASIC v1.1: 
<pre>|DRIVE,"A"
</pre>
or
<pre>
b$="test"
CALL or |RSX-command,@b$
</pre>

The parameters will be stored inside the range of Stack:
<pre>
     A=n -------> MSB PARAM1
                  LSB PARAM1
                  MSB PARAM2
                  LSB PARAM2
                  ...
                  ...
                  ...
                  MSB PARAMn
     IX+0 ------> LSB PARAMn
</pre>
with the help of that assembly code is it possible to find the parameters:
<pre>
ROUT1:  CP   x          ;test register A if "x" parameters were given, e.g. x = 2
        RET  NZ         ; if not exactly x parameters then do not execute RSX.
        LD   L,(IX+0)
        LD   H,(IX+1)   ; HL = value of last parameter        
        LD   E,(IX+2)
        LD   D,(IX+3)   ; DE = value of next to last parameter
        ...
</pre>
A register holds the number of parameters. IX points to each parameter. IX+0/IX+1 is the last parameter. This happens because each parameter in order is pushed onto the stack and IX then points to the last parameter pushed. Each parameter is a 16-bit value.

If a parameter is a string, then IX holds the address of the string descriptor which point to a 3 byte block. The first byte of the string descriptor is the length. The next 2 bytes are an address that point to the string in memory.

With the help of the variable container "@" it is also possible to get a result from an invoked mc-code back to basic.
In this case the parameter contains the address of the integer, floating point or string. You can modify these to give the result.
BASIC allocates the strings, so when you modify a string, do not write more characters than the original string.

Hint: the first two bytes at the end of stack shows the internal return address from BASIC interpreter where it was executed.

== Additional keywords and variables in BASIC v1.1  ==

#BASIC v1.1 has the following additional keywords: 
#*COPYCHR$ 
#*CURSOR 
#*DEC$ 
#*FILL 
#*FRAME 
#*GRAPHICS 
#*MASK 
#BASIC v1.1 has the following additional predefined variables: 
#*DERR

<br> <br> 

== BASIC programs  ==

A maximum of 255 characters can be entered for a single BASIC line.

There are some rules for assigning names for variables:
: - it is not allowed to define a variable starting with a figure (the system expect then programming mode and interpret it as a program line number)
: - no space (or 'under' as it is common today) between variable names are allowed
: - BASIC keywords can't be used
: - different sign e.g.: a slash (doesn't depend which direction), a 'minus' sign, a 'and' sign can't be used in a variable names
: - after a dollar sign (for defining string variables) it is not allowed to use further signs
: - different defining functions together are not allowed (e.g. use '%' together with '$')

: - you can use 40 characters for a variable name
: - use ! for defining a REAL value variable (like the function DEFREAL but only for the assigned variable) > It's also possible to omit the exlamation mark because it's the default system declaration after powering on then CPC.
: - use % for defining a INTEGER value variable (like the function DEFINT but only for the assigned variable)
: - use $ for defining a STRING variable (like the function DEFSTR but only for the assigned variable)
: - Minimum line number is 1. Maximum line number is 65535.

This is converted into the tokenised BASIC program which is more compact than the line entered. The BASIC keywords are converted into "tokens", or 1-2 byte sequences which uniquely identify each keyword. 

<br>

== Speeding up BASIC programs ==

To speed up BASIC programs following rules could help:
: - Avoid loops or a branching program structure if possible. Internally the operating system searches for the right line number always from the beginning of the program 'listing'. Often recurring subroutines  (if necessary) should be at the beginning of RAM to speed up things.
: - Avoid the index variable after the <code>NEXT</code> command/statement (although it isn't a good program style)
: - Avoid spaces inside program code or remarks
: - Put lots of statements as possible in ONE line
: - Use variables instead of constants. A constant has always to be converted in a binary/digital format. A variable is already converted.
: - Dimensioning at the beginning of the program
: - Dimensioning your variables & pre-calculate
: - Avoid AND/OR/XOR in IF-THEN statements. It's faster to write IF ... THEN (statement 1).. IF ... THEN (statement 2).
: - Minimise string/char manipulation as this often requires memory allocations. (e.g. joining strings with +, use of MID$, LEFT$, RIGHT$, SPACE$)

== Minimizing memory usage ==

To minimize memory usage in BASIC here are some things to consider.

The size of the tokenized program:
: - Difficult to measure without looking at the data in memory.
: - Use short variable names. The names are stored in the tokenized BASIC program as-is.
: - Minimize the number of variables. The names are stored in the tokenized BASIC program everywhere they are used.
: - Use as few lines as possible. It's a small saving of about 5 bytes per line.
: - Consider using numbers vs strings and potentially 8-bit or 16-bit values. 

Minimising memory usage when the program is running:
: - Minimize string operations. (e.g. A$=SPACE$(30)+CHR$(28) in memory this first allocates a string of length 30 containing spaces, then it allocates a new string of length 31 with spaces and char 28 at the end and assigns it to A$. In this line at least 30 bytes have been wasted. So consider if you need strings or perhaps if possible pre-define them).

== Structure of a BASIC program  ==

A BASIC program is stored in a tokenised format. Here the keywords are represented by 1 or 2 byte unique sequences. Each line of the BASIC program has the form: 

<br> 

{| border="1"
|-
! Offset 
! Size 
! Description
|-
| 0 
| 2 
| Length of line data in bytes (note 1)
|-
| 2 
| 2 
| 16-bit decimal integer line number (note 2)
|-
| 4 
| n 
| BASIC line encoded into tokens (note 3)
|-
| n+1 
| 1 
| "0" the end of line marker (note 4)
|}

<br> Notes: 

#This 16-bit value has two functions: if "0" it signals the end of the BASIC program. In this case, there is no furthur BASIC program lines or data, otherwise, this value defines the length of the tokenised BASIC program line in bytes, and includes the 2 bytes defining this value, the 2 bytes defining the program line number, and the end of line marker. This number is stored in little endian notation with low byte followed by high byte.
#This 16-bit value defines the line number and exists if the length of line data in bytes is not "0". A line number is a integer number in the range 1-65535. This number is stored in little endian notation with low byte followed by high byte. 
#This data defines the tokenised BASIC program line and exists if the length of line data in bytes is not "0". The length is dependant on the BASIC program line contents. 
#This value defines the end of the tokenised BASIC line data and exists if the length of line data in bytes is not "0". The BASIC interpreter looks for this token during the processing of this line, and if found, will stop execution and continue to the next line.

== BASIC GOSUB Subroutines ==

When Subroutines are used through the use of GOSUB, it's very important for that Subroutine to exit through the use of RETURN or if a Subroutine needs to GOTO somewhere else that, that place can RETURN. When a RETURN isn't found though, an area located at &AE8C in BASIC 1.0 or &AE70 in BASIC 1.1 then proceeds to fill with data from GOSUB calls and grows to the point over &1FF bytes have been used causing a MEMORY FULL error.

The Following example demonstrates how to Trap this error:

<pre>
100 DEFINT a-z:MODE 2
110 GOSUB 130
120 c=1:GOSUB 130:c=0:GOTO 110
130 IF c=0 THEN PRINT"*";:GOTO 120
140 RETURN
</pre>

When the MEMORY FULL is reached and MEMORY FULL occurs, the user can reveal the situation by executing a RETURN immediately following MEMORY FULL, in the example from above instead of getting Unexpected RETURN, the Code Prints a Star before returning to a MEMORY FULL state. In that example it doesn't take very long to reach a MEMORY FULL, though more substancial may take longer to reveal this error.

If a BASIC game should issue a MEMORY FULL error, the easiest test is to say RETURN. If Unexpected RETURN doesn't occur and the code tries to continue, it will be a sign of Subroutines not being able to RETURN after a GOSUB ia issued. The easiest course is to remove Subroutines. A game for example may have a series of GOSUBs going to a line checking IF something is true, and if so GOTO somewhere else where a RETURN may not be found. In those situations a GOSUB should be replaced with an IF...THEN..[line number] thus removing the Subroutine.

If you wish to know more about this please see my amended correction of the [[Amstrad Action December 1990 Type-Ins|Amstrad Action Issue 63 Type-Ins Game Madballs]]. The original game which was nicely coded, eventually ran into the problem of MEMORY FULL, though to fully reveal this error the game needed to be played for over 20 minutes. Another way to test for this error is to inspect the area of &AE8C to &B08B or &AE70 to &B06F depending on which version of BASIC is used.

== BASIC tokens  ==

This table list the BASIC tokens with no prefix byte. 

<br> 

{| border="1"
|-
! Code<br>(hexidecimal) 
! BASIC keyword
|-
| &amp;00 
| end of tokenised line marker
|-
| &amp;01 
| ":" statement seperator
|-
| &amp;02 
| integer variable definition (defined with "%" suffix)
|-
| &amp;03 
| string variable definition (defined with "$" suffix)
|-
| &amp;04 
| floating point variable definition (defined with "!" suffix)
|-
| &amp;05 
| var?
|-
| &amp;06 
| var?
|-
| &amp;07 
| var?
|-
| &amp;08 
| var?
|-
| &amp;09 
| var?
|-
| &amp;0a 
| var?
|-
| &amp;0b 
| variable definition (no suffix)
|-
| &amp;0c 
| variable definition (no suffix)
|-
| &amp;0d 
| variable definition (no suffix)
|-
| &amp;0e 
| number constant "0"
|-
| &amp;0f 
| number constant "1"
|-
| &amp;10 
| number constant "2"
|-
| &amp;11 
| number constant "3"
|-
| &amp;12 
| number constant "4"
|-
| &amp;13 
| number constant "5"
|-
| &amp;14 
| number constant "6"
|-
| &amp;15 
| number constant "7"
|-
| &amp;16 
| number constant "8"
|-
| &amp;17 
| number constant "9"
|-
| &amp;18 
| number constant "10"
|-
| &amp;19 
| 8-bit integer decimal value
|-
| &amp;1a 
| 16-bit integer decimal value
|-
| &amp;1b 
| 16-bit integer binary value (with "&amp;X" prefix)
|-
| &amp;1c 
| 16-bit integer hexadecimal value (with "&amp;H" or "&amp;" prefix)
|-
| &amp;1d 
| 16-bit BASIC program line memory address pointer (see notes)
|-
| &amp;1e 
| 16-bit integer BASIC line number
|-
| &amp;1f 
| floating point value
|-
| &amp;20 
| " " (space) symbol
|-
| &amp;21 
| ASCII "!" symbol
|-
| &amp;22 
| quoted string value
|-
| &amp;23-7b 
| ASCII printable symbols
|-
| &amp;7c 
| "&#124;" symbol; prefix for RSX commands
|-
| &amp;80 
| AFTER
|-
| &amp;81 
| AUTO
|-
| &amp;82 
| BORDER
|-
| &amp;83 
| CALL
|-
| &amp;84 
| CAT
|-
| &amp;85 
| CHAIN
|-
| &amp;86 
| CLEAR
|-
| &amp;87 
| CLG
|-
| &amp;88 
| CLOSEIN
|-
| &amp;89 
| CLOSEOUT
|-
| &amp;8a 
| CLS
|-
| &amp;8b 
| CONT
|-
| &amp;8c 
| DATA
|-
| &amp;8d 
| DEF
|-
| &amp;8e 
| DEFINT
|-
| &amp;8f 
| DEFREAL
|-
| &amp;90 
| DEFSTR
|-
| &amp;91 
| DEG
|-
| &amp;92 
| DELETE
|-
| &amp;93 
| DIM
|-
| &amp;94 
| DRAW
|-
| &amp;95 
| DRAWR
|-
| &amp;96 
| EDIT
|-
| &amp;97 
| ELSE
|-
| &amp;98 
| END
|-
| &amp;99 
| ENT
|-
| &amp;9a 
| ENV
|-
| &amp;9b 
| ERASE
|-
| &amp;9c 
| ERROR
|-
| &amp;9d 
| EVERY
|-
| &amp;9e 
| FOR
|-
| &amp;9f 
| GOSUB, GO SUB
|-
| &amp;a0 
| GOTO, GO TO
|-
| &amp;a1 
| IF
|-
| &amp;a2 
| INK
|-
| &amp;a3 
| INPUT
|-
| &amp;a4
| KEY
|-
| &amp;a5 
| LET
|-
| &amp;a6 
| LINE
|-
| &amp;a7 
| LIST
|-
| &amp;a8 
| LOAD
|-
| &amp;a9 
| LOCATE
|-
| &amp;aa 
| MEMORY
|-
| &amp;ab 
| MERGE
|-
| &amp;ac 
| MID$
|-
| &amp;ad 
| MODE
|-
| &amp;ae 
| MOVE
|-
| &amp;af 
| MOVER
|-
| &amp;b0 
| NEXT
|-
| &amp;b1 
| NEW
|-
| &amp;b2 
| ON
|-
| &amp;b3 
| ON BREAK
|-
| &amp;b4 
| ON ERROR GOTO, ON ERROR GO TO
|-
| &amp;b5 
| ON SQ
|-
| &amp;b6 
| OPENIN
|-
| &amp;b7 
| OPENOUT
|-
| &amp;b8 
| ORIGIN
|-
| &amp;b9 
| OUT
|-
| &amp;ba 
| PAPER
|-
| &amp;bb 
| PEN
|-
| &amp;bc 
| PLOT
|-
| &amp;bd 
| PLOTR
|-
| &amp;be 
| POKE
|-
| &amp;bf 
| PRINT
|-
| &amp;c0 
| "'" symbol (same function as REM keyword)
|-
| &amp;c1 
| RAD
|-
| &amp;c2 
| RANDOMIZE
|-
| &amp;c3 
| READ
|-
| &amp;c4 
| RELEASE
|-
| &amp;c5 
| REM
|-
| &amp;c6 
| RENUM
|-
| &amp;c7 
| RESTORE
|-
| &amp;c8 
| RESUME
|-
| &amp;c9 
| RETURN
|-
| &amp;ca 
| RUN
|-
| &amp;cb 
| SAVE
|-
| &amp;cc 
| SOUND
|-
| &amp;cd 
| SPEED
|-
| &amp;ce 
| STOP
|-
| &amp;cf 
| SYMBOL
|-
| &amp;d0 
| TAG
|-
| &amp;d1 
| TAGOFF
|-
| &amp;d2 
| TROFF
|-
| &amp;d3 
| TRON
|-
| &amp;d4 
| WAIT
|-
| &amp;d5 
| WEND
|-
| &amp;d6 
| WHILE
|-
| &amp;d7 
| WIDTH
|-
| &amp;d8 
| WINDOW
|-
| &amp;d9 
| WRITE
|-
| &amp;da 
| ZONE
|-
| &amp;db 
| DI
|-
| &amp;dc 
| EI
|-
| &amp;dd 
| FILL (v1.1)
|-
| &amp;de 
| GRAPHICS (v1.1)
|-
| &amp;df 
| MASK (v1.1)
|-
| &amp;e0 
| FRAME (v1.1)
|-
| &amp;e1 
| CURSOR (v1.1)
|-
| &amp;e2 
| (note 2)
|-
| &amp;e3 
| ERL
|-
| &amp;e4 
| FN
|-
| &amp;e5 
| SPC
|-
| &amp;e6 
| STEP
|-
| &amp;e7 
| SWAP
|-
| &amp;e8 
| (note 2)
|-
| &amp;e9 
| (note 2)
|-
| &amp;ea 
| TAB
|-
| &amp;eb 
| THEN
|-
| &amp;ec 
| TO
|-
| &amp;ed 
| USING
|-
| &amp;ee 
| &gt; (greater than)
|-
| &amp;ef 
| = (equal)
|-
| &amp;f0 
| &amp;gt=, &gt;&nbsp;=, =&gt; (greater or equal)
|-
| &amp;f1 
| &lt; (less than)
|-
| &amp;f2 
| &lt;&amp;gt, &lt;&nbsp;&gt; (not equal)
|-
| &amp;f3 
| =&lt;, &lt;=, &lt;&nbsp;= (less than or equal)
|-
| &amp;f4 
| + (addition)
|-
| &amp;f5 
| - (subtraction or unary minus)
|-
| &amp;f6 
| * (multiplication)
|-
| &amp;f7 
| / (division)
|-
| &amp;f8 
| ^ (x to the power of y)
|-
| &amp;f9 
| \ (integer division)
|-
| &amp;fa 
| AND
|-
| &amp;fb 
| MOD
|-
| &amp;fc 
| OR
|-
| &amp;fd 
| XOR
|-
| &amp;fe 
| NOT
|-
| &amp;ff 
| (prefix for additional keywords)
|}

<br> Notes: 

*The &amp;ff code is used as a prefix for more keywords. See the table below for the list of keywords using this prefix. 
*&amp;e2,&amp;e8 and &amp;e9 are not used 
*&amp;7c ("|") is a character prefix used to identify an RSX command. e.g. "|DIR". 

An RSX is encoded in a BASIC program using the following structure: 

{| border="1"
|-
! Offset 
! Count 
! Description
|-
| 0 
| 1 
| "&#124;" character prefix
|-
| 1 
| 1 
| 8-bit byte offset to tokens following RSX name.
|-
| 2 
| x 
| RSX name. (Last character of name has bit 7 set to "1", all other characters have bit 7 set to "0")
|}

*This token identifies a integer (16-bit) number. The two bytes following this token is the number, stored low byte then high byte. e.g. &amp;1a,&amp;2d,&amp;00 represents the integer number "&amp;002d"="45". 
*This token (&amp;0B) is changed at run-time to &amp;0D 
*This token identifies a integer variable. 02,00,00,var name offset to number in program setup when program RUN. The variable name is stored directly, with bit 7 of the last character set. 
*This token identifies a string variable. offset to string in program string stored AS IS with quotes around it. 
*This token identifies a floating point number. Immediatly following the token are 5 bytes which define the number.

{| border="1"
|-
! Offset 
! Count 
! Description
|-
| 0 
| 1 
| &amp;1f (note 1)
|-
| 1 
| 5 
| Floating point number (note 2)
|}

*#This byte is the BASIC token identifying a floating point number 
*#These 5 bytes define the floating point number. 
*The space symbol is used as a command seperator 
*Variable definitions: 
**The variable definition has the following structure:

{| border="1"
|-
! Offset 
! Count 
! Description
|-
| 0 
| 1 
| Token defining variable type
|-
| 2 
| 2 
| 16-bit Byte offset to variable value within tokenised BASIC program.
|-
| 4 
| x 
| Variable name
|}

<br> The 16-bit byte offset is initially set to 0, but is setup when the program is RUN. The offset is stored in little-endian format, with low byte followed by high byte. 

**The token byte defines the variable type (i.e. string, floating point, integer) and the suffix ("$", none and "%"). 
**The variable name is stored in the program, with bit 7 of the last character set to "1". e.g. The variable named "abc" will be encoded as 'a','b','c'+&amp;80 
*String values: 
**Each string value is prefixed with &amp;22 token. 
**All strings must be enclosed by double quote symbols (&amp;quot). This symbols define the start and end of the string value. 
**The string value can contain any symbol except the quote ("). i.e. 0-&amp;21, and &amp;23-&amp;ff can be used. 

*After running a program, Tokens of "1d" with 16-bit BASIC program line pointers are changed to token "1e" with the 16-bit memory address of the BASIC line number in memory.

<br> This table list the BASIC tokens with a &amp;ff prefix byte. 

<br> 

{| border="1"
|-
! Code<br>(hexidecimal) 
! BASIC keyword
|-
| &amp;00 
| ABS
|-
| &amp;01 
| ASC
|-
| &amp;02 
| ATN
|-
| &amp;03 
| CHR$
|-
| &amp;04 
| CINT
|-
| &amp;05 
| COS
|-
| &amp;06 
| CREAL
|-
| &amp;07 
| EXP
|-
| &amp;08 
| FIX
|-
| &amp;09 
| FRE
|-
| &amp;0a 
| INKEY
|-
| &amp;0b 
| INP
|-
| &amp;0c 
| INT
|-
| &amp;0d 
| JOY
|-
| &amp;0e 
| LEN
|-
| &amp;0f 
| LOG
|-
| &amp;10 
| LOG10
|-
| &amp;11 
| LOWER$
|-
| &amp;12 
| PEEK
|-
| &amp;13 
| REMAIN
|-
| &amp;14 
| SGN
|-
| &amp;15 
| SIN
|-
| &amp;16 
| SPACE$
|-
| &amp;17 
| SQ
|-
| &amp;18 
| SQR
|-
| &amp;19 
| STR$
|-
| &amp;1a 
| TAN
|-
| &amp;1b 
| UNT
|-
| &amp;1c 
| UPPER$
|-
| &amp;1d 
| VAL
|-
| &nbsp; 
| (note 2)
|-
| &amp;40 
| EOF
|-
| &amp;41 
| ERR
|-
| &amp;42 
| HIMEM
|-
| &amp;43 
| INKEY$
|-
| &amp;44 
| PI
|-
| &amp;45 
| RND
|-
| &amp;46 
| TIME
|-
| &amp;47 
| XPOS
|-
| &amp;48 
| YPOS
|-
| &amp;49 
| DERR (v1.1)
|-
| &nbsp; 
| (note 3)
|-
| &amp;71 
| BIN$
|-
| &amp;72 
| DEC$ (v1.1)
|-
| &amp;73 
| HEX$
|-
| &amp;74 
| INSTR
|-
| &amp;75 
| LEFT$
|-
| &amp;76 
| MAX
|-
| &amp;77 
| MIN
|-
| &amp;78 
| POS
|-
| &amp;79 
| RIGHT$
|-
| &amp;7a 
| ROUND
|-
| &amp;7b 
| STRING$
|-
| &amp;7c 
| TEST
|-
| &amp;7d 
| TESTR
|-
| &amp;7e 
| COPYCHR$ (v1.1)
|-
| &amp;7f 
| VPOS
|-
| &nbsp; 
| (note 4)
|}

<br> NOTES: 

*These codes are prefixed by &amp;FF. e.g. The keyword "ABS" is stored as the following sequence: <pre>&amp;FF,&amp;00</pre> 
*Codes &amp;1e...&amp;3f inclusive are not used 
*Codes &amp;4a...&amp;6f inclusive are not used 
*Codes &amp;80...&amp;ff inclusive are not used

*When a BASIC program is in memory, the BASIC ROM can replace "16-bit BASIC program line number" tokens with "16-bit BASIC program line memory address pointer".

When a program is loaded or saved, there will only be "16-bit BASIC program line number" tokens followed by a 16-bit number of the line.

When a program is running, BASIC will replace the "16-bit BASIC program line number" with the "16-bit BASIC program line memory address pointer" token, and replace the 16-bit line number with the memory address of the start of that line. 

It does this to avoid having to lookup the address of the line each time.

* When a REM or ' is seen, the characters following it are output directly (i.e. the bytes are not tokenized) until the end of line or a ':' is seen.

* When a BASIC program is listed each line is converted to a string (this includes the line number and the tokens converted to their strings). There is a maximum length for this string of 256 characters. This means that if the BASIC line is LISTed or EDITed, then the line will be displayed incorrectly with missing characters on the end. This is also noticed if you have a "10-liner" program that packs as much BASIC as possible into each line and renumber it so the line number has more digits.

== Floating Point data definition  ==

A floating point number represents a number with both an integer and fractional part. 

<br> In Amstrad BASIC, a floating point number is stored in base-2 in a normalized form: 1 x 2<sup>&lt;exponent&gt;</sup> The representation uses 5 bytes and is stored using the following structure: 

<br> 

{| border="1"
|-
! Byte 
! colspan="8" | 0 
! colspan="8" | 1 
! colspan="8" | 2 
! colspan="8" | 3 
! colspan="8" | 4
|-
! Bit 
! 7 
! 6 
! 5 
! 4 
! 3 
! 2 
! 1 
! 0 
! 7 
! 6 
! 5 
! 4 
! 3 
! 2 
! 1 
! 0 
! 7 
! 6 
! 5 
! 4 
! 3 
! 2 
! 1 
! 0 
! 7 
! 6 
! 5 
! 4 
! 3 
! 2 
! 1 
! 0 
! 7 
! 6 
! 5 
! 4 
! 3 
! 2 
! 1 
! 0
|-
| Function 
| colspan="8" | (LSB) mantissa (bits 31-24) 
| colspan="8" | mantissa (bits 23-16) 
| colspan="8" | mantissa (bits 15-8) 
| colspan="1" | sign 
| colspan="7" | (MSB) mantissa (bits 7-0) 
| colspan="8" | exponent
|}

=== Sign  ===

The sign is represented by bit 7 of byte 3. The value of the sign bit indicates the sign of the floating point number. 

*If the sign bit is "1", then the number is negative. 
*If the sign bit is "0", then the number is positive.

=== Mantissa  ===

The mantissa holds the normalized number. The exponent is manipulated so that the most significant bit is always 1. Since it is always 1, it is not stored. It's value is implied by the representation. 

=== Exponent  ===

The exponent is 8-bit and is stored in byte 4. It is stored with a bias of 128. 

*128-255 are positive exponents, 
*1-127 are negative exponents.
*0 means, the number is zero

To obtain the signed exponent, you must subtract 128 from the stored exponent. The minimum exponent is 1 and this describes a number of 2^-127. The maximum exponent is 255 and this describes a number of 2^127.
A value of 0 just means, that the number is zero (0).

=== BASIC Display of Floating point numbers ===

* Numbers are displayed to 9 decimal places.
* If the number doesn't have a fractional part (e.g. .0) then the fractional part is not displayed.
* Trailing zeros (zero digits after the last digit in the fraction) are not displayed
* The value is rounded in the following way for display:

If the 10th fractional digit is 5 or above, then the number is rounded up.
If the 10th fractional digit is 4 or below, then the number is rounded down.
e.g.  
 0.1234567891 is displayed as 0.123456789
 0.1234567895 is displayed as 0.12345679

=== floating point example in RAM by MaV ===

The initial figure = 43.375.
An example in BASIC:
<pre>
a!=43.375
READY
PRINT a!
 43.375
PRINT @a!
 374
FOR I=0 TO 4:PRINT HEX$(PEEK(374+I),2);:NEXT I
0000802D86
</pre>
the result for better readability:<br>
'''00 00 80 2D 86'''<br>
The first byte contains the least significant bits of the mantissa, and every following byte up to the fourth byte contain the bits following the first in significance and in exactly that order!

That means that you have to turn around the first four bytes if you want to read the mantissa correctly:
2D800000
or
0010.1101.1000.0000.0000.0000.0000.0000
in binary (the stops are inserted for better readability).

Now the highest significant bit here is 0, so the number is positive.
What's more, you need to clear that bit and substitute the implied highest bit (see description in the link), which is always 1 (regardless of the deleted sign bit!!!).
Thus you get:
AD800000
or
1010.1101.1000.0000.0000.0000.0000.0000
in binary.

The mantissa has an implied decimal point before the number. Since the number is 2^32 bits (i.e. 4 bytes) long you have to divide by 2^32 to get the proper decimal representation.

AD800000 (hex) = 2910846976 (dec)

2910846976 / 2^32 = 0.677734375

The mantissa in a decimal representation is: 0.677734375

Now, the last byte contains the exponent: 86 (hex) or 134 (dec). You need to subtract 128 to get the real exponent, the highest bit tells you that the exponent is positive (1) or negative (0). Your exponent is 6.

0.677734375 * 2^6 = 43.375

'''Another example:'''<br>
PI is represented in memory as:<br>
'''A2 DA 0F 49 82'''<br>
The mantissa is<br>
490FDAA2 (highest significant bit is zero => number is positive)
The exponent is<br>
82 (=positive mantissa, value=2 thus multiply mantissa with 2^2)<br>

Delete the sign bit (which is 0 anyway), and then add the implied 1 bit:<br>
C90FDAA2 (hex) = 3373259426 (dec) = 1100.1001.0000.1111.1101.1010.1010.0010 (bin)<br><br>

Calculate the decimal representation of the mantissa:<br>
3373259426 / 2^32 = 0,7853981633670628070831298828125<br><br>

Then add the exponent (82h - 80h = 2 thus 2^2)<br>
0,7853981633670628070831298828125 * 2^2 = 3,14159265346825122833251953125<br><br>

Voilà! The internal representation of the number PI on the CPC is: 3,14159265346825122833251953125<br><br>


If you compare to a (more) correct representation of PI, you'll see that the CPC is correct up to the 9th decimal place:<br><br>


CPC:<br>
3.14159265346825122833251953125<br>
more correctly:<br>
3.1415926535897932384626433832795028841971693993751058209749445923078164062862089986...

== BASIC floating-point/real variables  ==

A floating point (real) variable describes a number with integer and fractional parts. The biggest figure which can be stored correctly in RAM by a variable is 2^32-1 = 4294967295.

*A real variable is defined with a "!" character postfix.

e.g. 
<pre>a! = 3.141592654
</pre> 
*A real number uses 5 bytes of memory as storage. The format is described above. 
*The address of a real variable can be found in BASIC by: 
<pre>PRINT @a!
</pre>

Where "a" should be replaced with the name of the variable. 

<br>

== BASIC integer variables  ==

A integer variable describes a whole number. i.e. a number without any fractional part. 

<br> NOTES: 

*A integer variable is defined with a "%" character postfix.

e.g. 
<pre>a% = 3
</pre> 
*A integer variable has a range of -32768 to 32767 
*A integer variable always uses two bytes of memory as storage with the following format:

{| border="1"
|-
! Offset 
! Length 
! Description
|-
| 0 
| 2 
| Integer number
|}

*The address of the integer variable can be found in BASIC by: 
<pre>PRINT @a%
</pre>

where "a" should be replaced with the name of the variable.

== BASIC string variables  ==

A string is a variable which contains a group of characters. 

<br> NOTES: 

*A string variable is defined in BASIC with a "$" character postfix.

e.g. 
<pre>a$ = "hello"
</pre> 
*A string variable is described internally by a "string descriptor block" which has the following structure:

{| border="1"
|-
! Offset 
! Length 
! Description
|-
| 0 
| 1 
| Length of string in bytes/characters
|-
| 1 
| 2 
| Location of start of string
|}

*The address of the "string descriptor block" for the string variable can be found in BASIC by typing: 
<pre>PRINT @a$
</pre>

replacing "a$" with the name of the string variable. 

*A string uses a minimum of 3 bytes of storage (a 0 character length string) and a maximum of 258 bytes of storage. 3 bytes are used by the "string descriptor block") 
*A string variable can contain any ASCII character code in the range 0-255. 
*A string variable can store a minimum of 0 characters and a maximum of 255 characters. 
*The length of the string in characters is defined in the string descriptor block. The string does not have a termination character.

[[Category:Programming]]
[[Category:BASIC| ]]
[[Category:CPC Internal Components]]
[[Category:Operating System| ]]
[[Category:Software]]
[[Category:Programming software| ]]