Update

autismuk · autismuk · commit 36f12deb78c7 · 2023-02-27T15:46:39.000Z
diff --git a/reference/source/assembler.tex b/reference/source/assembler.tex
@@ -1,24 +1,24 @@
 \chapter{Inline Assembly}
 
-SuperBasic has a built in inline assembler, that is closely modelled on that of BASIC in the British Acorn machines (Atom, BBC Micro, Archimedes).\\
+SuperBASIC has a built in inline assembler, that is closely modelled on that of BASIC in the British Acorn machines (Atom, BBC Micro, Archimedes).\\
 
 \section{How it works}
 
 The way it works is that the instructions, named after their 65C02 opcode equivalents, generate code - so as a simple example the instruction "txa" generates the machine code \$8A in memory. If the instruction has an operand (say) "lda \#size*2" the expression is evaluated and the appropriate 2 bytes are stored in memory. \\
 
-Labels are specified using .<label name>, e.g. .loop ; this is equivalent to setting the variable 'loop' to the current write address, which can then be used in expressions - such as 'jmp loop'
+Labels are specified using .<label name>, e.g. .loop ; this is equivalent to setting the variable 'loop' to the current write address, which can then be used in expressions - such as 'jmp loop'.
 
 \section {The Assemble command}
 
 Assembly is controlled by the 'assemble' command. This has two parameters - the first indicates where the code is to be assembled in memory, and the second is a control byte. \\
 
-This has 2 bits.  Bit 0 indicates the pass, and if zero will not flag errors such as branches being out of range. Bit 1 , when set, causes the code generated by instructions like "txa"
+This has 2 bits.  Bit 0 indicates the pass, and if zero will not flag errors such as branches being out of range. Bit 1 , when set, causes the code generated by instructions like "txa".
 
 \begin{verbatim}
 	100 assemble $6000,2:lda #42:sta count:rts
 \end{verbatim}
 
-This very short example will assemble the 5 (or 4,depending on the value of count) bytes starting from \$6000 - and it also outputs those bytes to the screen. \\
+This very short example will assemble the 5 (or 4 depending on the value of count) bytes starting from \$6000 - and it also outputs those bytes to the screen. \\
 
 \section {Two pass Assembly}
 
diff --git a/reference/source/crossdev.tex b/reference/source/crossdev.tex
@@ -1,10 +1,10 @@
 \chapter{Cross Development of BASIC Programs}
 
-Cross development is an alternative to the classic way of programming a home computer, where the programmer types code directly into the machine. Cross development allows you to write the code on a Personal Computer, and upload it through the USB debug port in the F256. It is also possible to do this with machine code and graphic and other data.
+Cross development is an alternative to the classic way of programming a Home Computer, where the programmer types code directly into the machine. Cross development allows you to write the code on a Personal Computer, and upload it through the USB debug port in the F256. It is also possible to do this with machine code and graphic and other data.
 
 \section{Assistance}
 
-In the SuperBasic git, https://github.com/paulscottrobson/superbasic, each release contains a file "howto-crossdev-basic.zip" which gives everything you need to cross develop in BASIC and some example programs.
+In the SuperBASIC git, https://github.com/paulscottrobson/superbasic, each release contains a file "howto-crossdev-basic.zip" which gives everything you need to cross develop in BASIC and some example programs.
 
 \section{Connection}
 
@@ -18,7 +18,7 @@ \section{Software}
 
 \section{BASIC}
 
-The input to the program is standard ASCII files, with line numbers. Line numbers are required for editing only. (There is a python script on the superbasic github which adds these automatically). However, you do not need to use line numbers in programming, though GOTO and GOSUB are implemented if you wish, or want to port old software.
+The input to the program is standard ASCII files, with line numbers. Line numbers are required for editing only. (There is a python script on the SuperBASIC github which adds these automatically). However, you do not need to use line numbers in programming, though GOTO and GOSUB are implemented if you wish, or want to port old software.
 
 I would start with something simple though.
 
diff --git a/reference/source/f256jr_basic_ref.log b/reference/source/f256jr_basic_ref.log
@@ -1,4 +1,4 @@
-This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Arch Linux) (preloaded format=pdflatex 2023.2.26)  27 FEB 2023 08:13
+This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Arch Linux) (preloaded format=pdflatex 2023.2.26)  27 FEB 2023 15:46
 entering extended mode
  restricted \write18 enabled.
  %&-line parsing enabled.
@@ -823,9 +823,9 @@ Underfull \hbox (badness 10000) in paragraph at lines 9--10
  []
 
 
-Overfull \hbox (60.40598pt too wide) in paragraph at lines 11--12
-\T1/NotoSerif-TLF/m/n/10 line num-bers, there are some ex-am-ples of such at th
-e pri-mary github at http://github.com/paulscottrobson/superbasic
+Overfull \hbox (68.16174pt too wide) in paragraph at lines 11--12
+\T1/NotoSerif-TLF/m/n/10 line num-bers. There are some ex-am-ples of such at th
+e pri-mary github at http://github.com/paulscottrobson/SuperBASIC
  []
 
 
@@ -1194,8 +1194,8 @@ Overfull \hbox (10.0pt too wide) in paragraph at lines 1--1
  []
 
 
-Overfull \hbox (5.39339pt too wide) in paragraph at lines 7--8
-\T1/NotoSerif-TLF/m/n/10 In the Su-per-Ba-sic git, https://github.com/paulscott
+Overfull \hbox (8.84857pt too wide) in paragraph at lines 7--8
+\T1/NotoSerif-TLF/m/n/10 In the Su-per-BA-SIC git, https://github.com/paulscott
 robson/superbasic, each re-lease con-tains a file "howto-
  []
 
@@ -1265,7 +1265,7 @@ f-Italic.pfb></usr/share/texmf-dist/fonts/type1/google/noto/NotoSerif-Regular.p
 fb></usr/share/texmf-dist/fonts/type1/public/cm-super/sftt1000.pfb></usr/share/
 texmf-dist/fonts/type1/public/newtx/txsys.pfb></usr/share/texmf-dist/fonts/type
 1/urw/zapfchan/uzcmi8a.pfb>
-Output written on f256jr_basic_ref.pdf (47 pages, 221124 bytes).
+Output written on f256jr_basic_ref.pdf (47 pages, 221130 bytes).
 PDF statistics:
  801 PDF objects out of 1000 (max. 8388607)
  728 compressed objects within 8 object streams
diff --git a/reference/source/f256jr_basic_ref.pdf b/reference/source/f256jr_basic_ref.pdf
diff --git a/reference/source/f256jr_basic_ref.synctex.gz b/reference/source/f256jr_basic_ref.synctex.gz
diff --git a/reference/source/f256jr_basic_ref.tex b/reference/source/f256jr_basic_ref.tex
@@ -22,13 +22,13 @@
 \newcommand{\example}[1]{\subsection*{Example: #1}}
 \begin{document}
 
-\title{Foenix \jr\ BASIC Reference Manual}
+\title{F256  Reference Manual}
 \author{Peter Weingartner}
 \begin{titlepage}
     \colorbox{silver}{\makebox[\textwidth][r]{
     \shortstack{
         \vspace{3cm} \\
-        \color{darkblue}\bfseries\sffamily\Huge Foenix \jr\ BASIC Reference Manual}} \\
+        \color{darkblue}\bfseries\sffamily\Huge F256 SuperBASIC Reference Manual}} \\
     }
 
     \vfill
diff --git a/reference/source/introduction.tex b/reference/source/introduction.tex
@@ -4,11 +4,11 @@ \section{Introduction}
 
 This document is not a tutorial and assumes the reader has some knowledge of programming in general and BASIC in particular. \\
 
-If you want to learn programming, I would advise you try learning using one of the numerous courses available. The course in the Vic20 manual is highly regarded and can be used with an emulator such as Vice, and much of the knowledge will transfer directly.\\
+If you want to learn programming, I would advise you try learning using one of the numerous courses available. The course in the Vic20 manual is highly regarded and can be used with an emulator such as "Vice", and much of the knowledge will transfer directly.\\
 
-F256's SuperBASIC is a modernised BASIC interpreter for the 65C02 processor. It currently occupies 4 pages (32k) of Flash, mapped into 2 pages (16k) of the 65C02 memory space. At present, this is from $8000-$BFFF.\\
+F256's SuperBASIC is a modernised BASIC interpreter for the 65C02 processor. It currently occupies 4 pages (32k) of Flash mapped into 2 pages (16k) of the 65C02 memory space. At present, this is from $8000-$BFFF.\\
 
-Currently editing is still done using line numbers, however it is possible to cross-develop without line numbers, there are some examples of such at the primary github at http://github.com/paulscottrobson/superbasic under the 'games' directory.\\
+Currently editing is still done using line numbers, however it is possible to cross-develop without line numbers. There are some examples of such at the primary github at http://github.com/paulscottrobson/SuperBASIC under the 'games' directory.\\
 
 However, there is no requirement to actually use them in programs. GOTO, GOSUB and RETURN are supported but this is more for backwards compatibility with older programs. It is advised to use Procedures, For/Next, While, Repeat and If/Else/Endif commands for better programming and clarity.\\
 
@@ -32,7 +32,7 @@ \section{Memory usage}
 
 \section{Memory usage elsewhere}
 
-SuperBasic uses memory locations outside the normal 6502 address space as well. \\
+SuperBASIC uses memory locations outside the normal 6502 address space as well. \\
 
 If you use a bitmap, it will be placed at \$10000 in physical space and occupy 320x240 bytes.\\
 
diff --git a/reference/source/procedures.tex b/reference/source/procedures.tex
@@ -1,10 +1,10 @@
 \chapter{Structured Programming}
 
-SuperBasic is designed for better and more readable programs. If you learnt BASIC on another machines, you will mostly have used GOTO, GOSUB and RETURN.\\
+SuperBASIC is designed for better and more readable programs. If you learnt BASIC on another machines, you will mostly have used GOTO, GOSUB and RETURN.\\
 
 These are terrible.\\
 
-SuperBasic does support these, but it is strongly advised you do not use them. However, they can be useful for running old code. SuperBasic is not Microsoft BASIC compatible, but is close enough so that code will normally work with minor alterations.
+SuperBASIC does support these, but it is strongly advised you do not use them. However, they can be useful for running old code. SuperBASIC is not Microsoft BASIC compatible, but is close enough so that code will normally work with minor alterations.
 
 \section{Named procedures}
 
diff --git a/reference/source/programs.tex b/reference/source/programs.tex
@@ -7,12 +7,12 @@ \chapter{Writing Programs in SuperBASIC}
 
 It is easy to cross develop in SuperBASIC (see later), writing a program on your favourite text editor, and squirting it down the USB cable using the Python script fnxmgr , or the Foenix IDE. It is also possible to develop without line numbers and have them added as the last stage before uploading.\\
 
-Upper and Lower case is considered to be the same, so variable myName and MYNAME and MyName are all the same variable. The only place where case is specifically differentiated is in string constants.\\
+Upper and Lower case is considered to be the same, so variable myName, MYNAME and MyName are all the same variable. The only place where case is specifically differentiated is in string constants.\\
 
 Programs can be loaded or saved to SD Card or to an IEC type drive (the 5 pin DIN serial port) using the SAVE and LOAD command.\\
 
 There is also currently a VERIFY command whose purpose it is to check files have been saved correctly. While the SD Card and IEC code has been seen to be reliable in practice, the code is still relatively new ; so when saving BASIC programs in development, I recommend saving them under incremental names (e.g. prog1.bas, prog2.bas) , verifying them, and periodically backing up your SD card.\\
 
 This may seem slightly long winded, but is a good defensive measure as there may be bugs in the kernel routines, or the BASIC routines which handle program editing. \\
 
-The documents directory in the SuperBasic github, which is publicly accessible, has a simple syntax highlighter for the Sublime Text editor.\\
+The documents directory in the SuperBASIC github, which is publicly accessible, has a simple syntax highlighter for the Sublime Text editor.\\
diff --git a/reference/source/reference.tex b/reference/source/reference.tex
@@ -13,7 +13,7 @@ \section*{!}
 40 a!b=12
 \end{verbatim}
 
-\section*{' and Rem}
+\section*{' and rem}
 Comment. ‘ and rem are synonyms.  The rest of the line is ignored. The only difference between the two is when listing, ‘ comments show up in reverse to highlight them. Remarks should be in quotes for syntactic consistency.
 
 \example{Simple comments}
diff --git a/reference/source/sound.tex b/reference/source/sound.tex
@@ -4,15 +4,15 @@ \section{Introduction}
 
 The F256Jr has 2 independent SN76489 sound chips, for left and right channel, and optionally 2 further SID chips or SID chip clones.
 
-For the purpose of sound these are simplified, so the same tones are played on left or right channels simultaneously.
+In SuperBASIC these are simplified, so the same tones are played on left or right channels simultaneously.
 
 \section{Channels}
 
 There are four sound channels, numbered 0 to 3. 0 to 2 are simple square wave channels, the 3rd is a sound channel.
 
 Sounds have a queue of sounds to play. So you could queue up a series of notes to play and they will carry on playing one after the other (if they are on the same channel). 
 
-BASIC does not stop to play the sounds ; it is processed in the background. Everything can be silenced with 'sound off'.
+SuperBASIC does not stop to play the sounds ; it is processed in the background. Everything can be silenced with 'sound off'.
 
 It is possible to set a parameter to automatically change the pitch of the channel as it plays to allow easy creation of simple warpy sound effects.
 
diff --git a/reference/source/sprites.tex b/reference/source/sprites.tex
@@ -16,7 +16,7 @@ \section{Introduction}
 
 \section {Creating sprites}
 
-In SuperBASIC sprite data is loaded, with an index, to memory location \$30000. This chapter explains how to create that index.
+SuperBASIC by default loads sprite data to memory location \$30000. This chapter explains how to create that data file.  This can be done by the developer, or via a python script.
 
 \section{Getting images}
 
@@ -59,6 +59,6 @@ \section{Data format}
 +03 the first byte of sprite data 
 \end{verbatim}
 
-the size, LUT and data are then repeated for every sprite in the sprite set. The file should end with a sprite size of \$80 (128) to indicate the end of the set.
+The size, LUT and data are then repeated for every sprite in the sprite set. The file should end with a sprite size of \$80 (128) to indicate the end of the set.
 
 
diff --git a/reference/source/tiles.tex b/reference/source/tiles.tex
@@ -2,7 +2,7 @@ \chapter{Tiles and Tile Maps}
 
 \section{Introduction}
 
-SuperBasic supports a single tile map, made up of 8x8 pixel images. A tile map can be up to 255 x 255 tiles in size.
+SuperBASIC supports a single tile map, made up of 8x8 pixel images. A tile map can be up to 255 x 255 tiles in size.
 
 \section{Setting up a Tile Map}
 
diff --git a/reference/source/variables.tex b/reference/source/variables.tex
@@ -2,7 +2,7 @@ \chapter{Identifiers, Variables and typing}
 
 \section{Procedure and variable naming}
 
-SuperBasic allows full naming of both variables and procedures (a type of 'subroutine').\\
+SuperBASIC allows full naming of both variables and procedures (a type of 'subroutine').\\
 A name begins with an alphabetic character or underscore, and continues with either alphanumeric character or underscores. They may also have a type character (\$ ( or \#) e.g.
 
 \begin{verbatim}
@@ -16,11 +16,11 @@ \section{Procedure and variable naming}
 
 This allows you to write readable code ; no more trying to remember what C7 is\\
 
-An implementation note ; when the program is stored in memory, it only keeps one copy of the actual identifier 'text' name, irrespective of how many times you use it. So there apart from that once, there is no space saving from using long identifier names.
+An implementation note: when the program is stored in memory, it only keeps one copy of the actual identifier 'text' name, irrespective of how many times you use it. So there apart from that once, there is no space saving from using long identifier names.
 
 \section{Types}
 
-Variable in SuperBasic are one of three types - integers, floating point and strings.\\
+Variable in SuperBASIC are one of three types - integers, floating point and strings.\\
 
 By default a variable holds an integer, which is a number between about -2 billion and +2 billion (technically it's a 32 bit integer).\\
 
@@ -38,7 +38,7 @@ \section{Types}
 
 \section{Arrays}
 
-Arrays are a collection of variables, stored under one name. SuperBasic supports up to two dimensions of arrays, with a maximum of 254 elements in each dimension. Arrays are indexed from zero.
+Arrays are a collection of variables, stored under one name. SuperBASIC supports up to two dimensions of arrays, with a maximum of 254 elements in each dimension. Arrays are indexed from zero.
 
 \begin{verbatim}
 	100 dim a$(3)
