diff --git a/docs/gbz80.7.pdf b/docs/gbz80.7.pdf index 2a0ff894..4707f72a 100644 Binary files a/docs/gbz80.7.pdf and b/docs/gbz80.7.pdf differ diff --git a/docs/rgbasm.1.html b/docs/rgbasm.1.html index ac62885a..66eb7a69 100644 --- a/docs/rgbasm.1.html +++ b/docs/rgbasm.1.html @@ -333,6 +333,10 @@
-Wunmapped-char=2
warns if the
active charmap is empty, and/or is not the default charmap
‘main’.
+ -Wunterminated-load
LOAD
block is not terminated by an
+ ENDL
. This warning is enabled by
+ -Wextra
.-Wno-user
WARN
built-in is executed. (See
“Aborting the assembly process” in
diff --git a/docs/rgbasm.1.pdf b/docs/rgbasm.1.pdf
index 74f58a76..348a01dc 100644
Binary files a/docs/rgbasm.1.pdf and b/docs/rgbasm.1.pdf differ
diff --git a/docs/rgbasm.5.html b/docs/rgbasm.5.html
index a6f55810..bfc66c0a 100644
--- a/docs/rgbasm.5.html
+++ b/docs/rgbasm.5.html
@@ -1153,7 +1153,7 @@ A LOAD
block feels similar to a
SECTION
declaration because it creates a new one.
@@ -1186,12 +1186,19 @@
In the example above, all of the code and data will end up in the - "LOAD example" section. You will notice the + “LOAD example” section. You will notice the ‘RAMCode’ and ‘RAMLocation’ labels. The former is situated in ROM, where the code is stored, the latter in RAM, where the code will be loaded.
You cannot nest LOAD
blocks, nor can you
change or stop the current section within them.
The current LOAD
block can be ended by
+ using ENDL
. This directive is only necessary if you
+ want to resume writing code in its containing ROM section. Any of
+ LOAD
, SECTION
,
+ ENDSECTION
, or POPS
will end
+ the current LOAD
block before performing its own
+ function.
LOAD
blocks can use the
UNION
or FRAGMENT
modifiers,
as described below.