RTR logo


BBC BASIC (86) Manual

Format of Program and Variables in Memory

Annex D to

Memory Map

There are significant differences between BBCBASIC and BIGBASIC. The general description is applicable to both versions, but the memory map and the format of variables in memory are different. You should refer to the annex entitled BIGBASIC for details.

BBCBASIC(86) runs under the MS-DOS (PC DOS) operating system. It requires about 32 kbytes of code space. The interpreter's code segment and data segment addresses are different and 64 kbytes of memory are available on most systems for the interpreter's variables and your BBCBASIC(86) program.

The interpreter's internal variables and programmable character definitions occupy &900 bytes of memory (default setting of PAGE) and this leaves &F700 (63232) bytes for your program and its variables in a computer with about 132k of memory. The exact memory requirement for a full 64 kbytes depends on the room taken up by your version of MS-DOS (PC DOS) and the way you have configured your computer (CONFIG.SYS and AUTOEXEC.BAT).

BBCBASIC(86) releases any memory surplus to its requirements so that other programs can be run from within BBCBASIC(86) using 'star' commands (see the Operating System Interface section for details).

By default, your program will start on the page boundary immediately following the interpreter's data area and the 'dynamic data structures' will immediately follow your program. The total group of the dynamic data structures is called the 'heap'. The base of the program control stack is located at HIMEM. HIMEM is usually at &10000, but it will probably be lower on computers with less than 128k of memory. (See above.)

As your program runs, the heap expands upwards towards the stack and the stack expands downwards towards the heap. If the two should meet, you get a 'No room' error. Fortunately, there is a limit to the amount by which the stack and the heap expand.

In general, the heap only expands whilst new variables are being declared. However, bad management of string variables can also cause the heap to expand.

In addition to running your program, the stack is also used 'internally' by the BBCBASIC(86) interpreter. Its size fluctuates but, in general, it expands every time you increase the depth of nesting of your program structure and every time you increase the number of local variables in use.

BBCBASIC(86) Work Space

Start of program
User defined characters
Function key strings
Interpreter's internal variables

Workspace RAM

BBCBASIC(86) uses 1024 (&400) bytes of RAM as a workspace. It contains the values of resident interpreter variables, LOMEM, HIMEM, etc. The full list is as follows, where the addresses are offsets from the start of the data segment.
&00-&6B The static variables. 108 bytes holding the values of the 27 integer variables @% to Z% inclusive. The variable values are stored as described later in this Annex and they each occupy 4 bytes.
&6C-&D7 54 2-byte values (108 bytes in all) which point to the first item in the linked lists of dynamic variables starting with the characters A to Z (26) and _ to z (28). If no variables starting with the given initial character exists, the pointer contains zero.
&D8-&D9 A 2-byte pointer to the linked list of function names, If no function is currently active, this contains zero.
&DA-&DB A 2-byte pointer to the linked list of procedure names. If no procedure is currently active, this contains zero.
&DC-&DD The 2-byte value of PAGE.
&DE-&DF The 2-byte value of TOP (TOP > PAGE).
&E0-&E1 The 2-byte value of LOMEM.
&E2-&E3 A 2-byte pointer to the first free location after the heap.
&E4-&E5 The 2-byte value of HIMEM (LOMEM <= FREE < HIMEM).
&E6-&E7 The 2-byte value of the stack pointer when an ON ERROR LOCAL statement is executed.
&E8-&E9 A 2-byte value holding the current TRACE status. TRACE OFF sets it to zero, TRACE ON to &FFFF and TRACE nnn sets it to nnn (line numbers less than nnn are traced).
&EA-&EB A 2-byte value holding the current AUTO line number. If zero, AUTO is not active.
&EC-&ED A 2-byte pointer to the tail of the ON ERROR statement in the user's program. If zero, no ON ERROR statement is active (ON ERROR OFF).
&EE-&EF A 2-byte pointer to the last error string (used by REPORT).
&F0-&F1 A 2-byte pointer to the current DATA item in the user's program. Initialised to point to the first data item (if any) when the program is RUN.
&F2-&F3 The 2-byte value of ERL (the line number at which the last error occurred).
&F4-&F5 BASIC copies the program text pointer to this location every so often (at the beginning of each line, for example). When an error occurs, it is used to determine ERL.
&F6-&FA A 33 bit pseudo random number updated by RND. Five bytes are used to hold this number, the fifth byte containing only the 33rd bit.
&FB The 1-byte value of COUNT (the number of printed characters output since the last new line).
&FC The 1-byte value of WIDTH. Zero signifies that BBCBASIC(86) inserts no automatic new-lines.
&FD The 1-byte value of ERR (the number of the last error).
&FE A byte containing the LISTO value.
&FF A 1-byte value containing the increment for the AUTO command.
&100-&1FF The string accumulator.
&200-&2FF The input buffer.
&300-&36F Miscellaneous and graphics workspace (112 bytes).
&370-&39F The 48-byte SOUND buffer.
&3A0-&3BF 32-bytes of ENVELOPE storage.
&3C0-&3FF A 64-byte path/filename buffer.
User's Program
Interpreter's workspace
&10000 (if sufficient memory)
Current limit of stack
Current limit of heap
Heap base/end of program
Start of program at &900

The Memory Map

The function of HIMEM, LOMEM, TOP and PAGE are briefly discussed below. You will find more complete definitions elsewhere in this manual. You can directly set HIMEM, LOMEM and PAGE. However, for most of your programs you won't need to alter any of them. You will probably only need to change HIMEM if you want to put some machine code sub-routines at the top of memory.

HIMEM The first address at the top of memory which is not available for use by BBCBASIC(86). The base of the program stack is set at HIMEM. (The first 'thing' stored on the stack goes at HIMEM-1.)
LOMEM The start address for the heap. The first of the dynamic data structures starts at LOMEM.
TOP The first free location after the end of your program. Unless you have set LOMEM yourself, LOMEM=TOP. You cannot directly set TOP. It alters as you enter your program. The current length of your program is given by:
PAGE The address of the start of your program. You can place several programs in memory and switch between them by using PAGE. Don't forget to control LOMEM as well. If you don't, the heap for one program might overwrite another program.

Memory Management

There is little you can do to control the growth of the stack. However, with care, you can control the growth of the heap. You can do this by limiting the number of variables you use and by good string variable management.

Limiting the Number of Variables

Each new variable occupies room on the heap. Restricting the length of the names of variables and limiting the number of variables used will limit the size of the heap. However, of the techniques available to you, this is the least rewarding. In addition, it leads to incomprehensible programs because your variable names become meaningless. You should keep this technique in the back of your mind whilst you are programming, but only apply it rigorously if you are really stuck for space.

String Management

Garbage Generation

Unlike numeric variables, string variables do not have a fixed length. When you create a string variable it is added to the heap and sufficient memory is allocated for the initial value of the string. If you subsequently assign a longer string to the variable there will be insufficient room for it in its original position and the string will have to be relocated with its new value at the top of the heap. The initial area will then become 'dead' and the heap will have grown by the new length of the string. The areas of 'dead' memory are called garbage. As more and more re-assignments take place, the heap grows and eventually there is no more room. Thus, it is possible to run out of room for variables even though there should be enough space.

Memory Allocation for String Variables

You can overcome the problem of 'garbage' by reserving enough memory for the longest string you will ever put into a variable before you use it. You do this simply by assigning a string of spaces to the variable. If your program needs to find an empty string the first time it is used, you can subsequently assign a null string to it. The same technique can be used for string arrays. The example below sets up a single dimensional string array with room for 20 characters in each entry, and then empties it.
10 DIM names$(10)
20 FOR i=0 TO 10
30   name$(i)=STRING$(20," ")
50 stop$=""
60 FOR i=0 TO 10
70   name$(i)=""
Assigning a null string to stop$ prevents the space for the last entry in the array being recovered when it is emptied.

Program Storage in Memory

The program is stored in memory in the format shown below. The first program line commences at PAGE.

length LSB MSB token       : token     &0D
      Up Reserved Word Tokens Up     CR
  Line No Left Program Line Right  

Line Length

The line length includes the line length byte. The address of the start of the next line is found by adding the line length to the address of the start of the current line. The end of the program is indicated by a line length of zero and a line number of &FFFF.

Line Number

The line number is stored in two bytes, LSB first. The end of the program is indicated by a line number of &FFFF and a line length of zero.


With the exception of the symbols '*', '=' and '[' and the optional reserved word LET, each statement in the line commences with the appropriate reserved word token. Reserved words are tokenised wherever they occur. A token is indicated by bit 7 of the byte being set. Statements within a line are separated by colons.

Line Terminator

Each program line (except the last) is terminated by a carriage-return (&0D).

Variable Storage in Memory

Variables are held within memory as linked lists (chains). The first variable in each chain is accessed via an index which is maintained by BBCBASIC(86). There is an entry in the index for each of the characters permitted as the first letter of a variable name. Each entry in the index has a word (two bytes) address field which points to the first variable in the linked list with a name starting with its associated character. If there are no variables with this character as the first character in the name, the pointer word is zero. The first word of all variables holds the address of the next variable in the chain. The address word of the last variable in the chain is zero. All addresses are held in the standard 8086 format - LSB first.

The first variable created for each starting character is accessed via the index and subsequently created variables are accessed via the index and the chain. Consequently, there is some speed advantage to be gained by arranging for all your variables to start with a different character. Unfortunately, this can lead to some pretty unreadable names and programs.

Integer Variables

Integers are held in two's complement format. They occupy 4 bytes, with the LSB first. Bit 7 of the MSB is the sign bit. To make up the complete variable, the address word, the name and a separator (zero) byte are added to the number. The format of the memory occupied by an integer variable called 'NUMBER%' is shown below. Note that since the first character of the name is found via the index, it is not stored with the variable.

LSB MSB U M B E R % &00 LSB     MSB
Up Up Left Rest of Name Right   Left Value Right
Address of next variable
starting with the same letter

The smallest amount of space is taken up by a variable with a single letter name. The static integer variables, which are not included in the variable chains, use the names A% to Z%. Thus, the only single character names available for dynamic integer variables are a% to z% plus _% and `% (CHR$(96)). As shown below, integer variables with these names will occupy 8 bytes.

LSB MSB % &00 LSB     MSB
Up Up     Left Value Right
Address of next variable
starting with the same letter

Real Variables

Real numbers are held in binary floating point format. The mantissa is held as a 4 byte binary fraction in sign and magnitude format. Bit 7 of the MSB of the mantissa is the sign bit. When working out the value of the mantissa, this bit is assumed to be 1 (a decimal value of 0.5). The exponent is held as a single byte in 'excess 127' format. In other words, if the actual exponent is zero, the value of stored in the exponent byte is 127. To make up the complete variable, the address word, the name and a separator (zero) byte are added to the number. The format of the memory occupied by a real variable called 'NUMBER' is shown below.

Up Up Left Rest of Name Right   Left Mantissa Right Up
Address of next variable Exponent
starting with the same letter

As with integer variables, variables with single character names occupy the least memory. (However, the names A to Z are available for dynamic real variables.) Whilst a real variable requires an extra byte to store the number, the '%' character is not needed in the name. Thus, integer and real variables with the same name occupy the same amount of memory. However, this does not hold for arrays, since the name is only stored once.

In the following examples, the bytes are shown in the more human-readable manner with the MSB on the left.

The value 5.5 would be stored as shown below.

Mantissa   Exponent  
.0011 00000000 00000000 00000000 0000 1000 0010
UpSign Bit  
&3000 0000&82
Because the sign bit is assumed to be 1, this would become:
Mantissa   Exponent  
.1011 00000000 00000000 00000000 0000 1000 0010
&B000 0000&82
The equivalent in decimal is:
     (0.5+0.125+0.0625) * 2^(130-127)
=   0.6875 * 2^3
=   0.6875 * 8
=   5.5
BBCBASIC(86) stores integer values in real variables in a special way which allows the faster integer arithmetic routines to be used if appropriate. The presence of an integer value in a real variable is indicated by the stored exponent being zero. Thus, if the stored exponent is zero, the real variable is being used to hold an integer and the 4 byte mantissa holds the number in normal integer format.

Depending on how it is put there, an integer value can be stored in a real variable in one of two ways. For example,

will set the exponent to zero and store the integer &00 00 00 05 in the mantissa. On the other hand,
will set the exponent to &82 and the mantissa to &20 00 00 00.

The two ways of storing an integer value are illustrated in the following four examples.
Example 1
  number=5       & 0000000005 Integer 5
Example 2
  number=5.0 & 8220000000 Real 5.0
This is treated as
  & 82A0000000  
because the sign bit is assumed to be 1.
Example 3
  number=-5 & 00FFFFFFFB  
The 2's complement gives
  & 0000000005 Integer -5
Example 4
  number=-5.0 & 82A0000000 Real -5.0
(The sign bit is already 1)
Magnitude =

If all this seems a little complicated, try using the program on the next page to accept a number from the keyboard and display the way it is stored in memory. The program displays the 4 bytes of the mantissa in 'human readable order' followed by the exponent byte. Look at what happens when you input first 5 and then 5.0 and you will see how this corresponds to the explanation given above. Then try -5 and -5.0 and then some other numbers. (The program is an example of the use of the byte indirection operator. See the Indirection section for details.)

The layout of the variable 'NMBR' in memory is shown below.

  Up   Up    
A%-5 points here A%-2 points here Up  
A%-1 points here Up
A% points here  

 10 NUMBER=0
 20 DIM A% -1
 50   PRINT "& ";
 60   :
 70   REM Step through mantissa from MSB to LSB
 80   FOR I%=2 TO 5
 90     REM Look at value at address A%-I%
100     NUM$=STR$~(A%?-I%)
110     IF LEN(NUM$)=1 NUM$="0"+NUM$
120     PRINT NUM$;" ";
130   NEXT
140   :
150   REM Look at exponent at address A%-1
160   N%=A%?-1
170   NUM$=STR$~(N%)
180   IF LEN(NUM$)=1 NUM$="0"+NUM$
190   PRINT " & "+NUM$''

String Variables

String variables are stored as the string of characters. Since the current length of the string is stored in memory an explicit terminator for the string in unnecessary. As with numeric variables, the first word of the complete variable is the address of the next variable starting with the same character. However, since BBCBASIC(86) needs information about the length of the string and the address in memory where the it starts, the overheads for a string are more than for a numeric. The format of a string variable called 'NAME$' is shown below.

LSB MSB A M E $ &00 len max LSB MSB
Up Up Left Rest of name Right   Up   Up Up
Address of next variable Current string length String start address
starting with the same letter Max (original) length Up    

When a string variable is first created in memory, the characters of the string follow immediately after the two bytes containing the start address of the string and the current and maximum lengths are the same. While the current length of the string does not exceed its length when created, the characters of the string will follow the address bytes. When the string variable is set to a string which is longer than its original length, there will be insufficient room in the original position for the characters of the string. When this happens, the string will be placed on the top of the heap and the new start address will be loaded into the two address bytes. The original string space will remain, but it will be unusable. This unusable string space is called 'garbage'. See the Variables sub-section for ways to avoid creating garbage.

Because the original length and the current length of the string are each stored in a single byte in memory, the maximum length of a string held in a string variable is 255 characters.

Fixed Strings

You can place a string starting at a given location in memory using the indirection operator '$'. For example,
$&8000="This is a string"
would place &54 (T) at address &8000, &68 (h) at address &8001, etc. Because the string is placed at a predetermined location in memory it is called a 'fixed' string. Fixed strings are not included in the variable chains and they do not have the overheads associated with a string variable. However, since the length of the string is not stored, an explicit terminator (&0D) is used. Consequently, in the above example, byte &8010 would be set to &0D.



Best viewed with Any Browser Valid HTML 3.2!
© Doug Mounter and Richard Russell 1999