<sect>Use the preincrement and predecrement operators<p>
-The compiler not always smart enough to figure out, if the rvalue of an
+The compiler is not always smart enough to figure out, if the rvalue of an
increment is used or not. So it has to save and restore that value when
producing code for the postincrement and postdecrement operators, even if this
value is never used. To avoid the additional overhead, use the preincrement
location on the stack when needed.
Because of this additional code, accessing the fixed parameters in a variadic
-function is much more expensive than access to parameters in a "normal"
+function is much more expensive than access to parameters in a "normal"
function. Unfortunately, this additional code is also invisible to the
programmer, so it is easy to forget.
<tscreen><verb>
System error at:xxxx
</verb></tscreen>
-where <tt/xxxx/ is last known execution address (caller). By default this is binded to <tt/BRK/
+where <tt/xxxx/ is last known execution address (caller). By default this is bound to <tt/BRK/
instruction, but it might be usable in debugging as kind of <tt/assert/.
<p>
System is halted after call to <tt/Panic/.
<sect>Library Structures
<p>
To simplify usage and optimize passing parameters to functions I have declared several structures
-which describe most common objects. Some of these structures are binded to static addresses in
+which describe most common objects. Some of these structures are bound to static addresses in
GEOS data space ($8000-$8fff), so you can use their fields directly in optimized way.
Please see <tt/gsym.h/ and find them. All structures are defined in <tt/gstruct.h/ and you may
find also some comments there.
<sect2>fontdesc
<p>
This structure describes a font in one pointsize. There is current font - <tt/struct fontdesc/
-binded at <tt/curFontDesc/. You can also force GEOS to use your own fonts by calling
+bound to <tt/curFontDesc/. You can also force GEOS to use your own fonts by calling
<tt/LoadCharSet/. You just need to open a VLIR font file and load one record - one pointsize
somewhere. At the start of this area you already have all data for <tt/fontdesc/ so you can
pass a pointer to the load adress of that pointsize to <tt/LoadCharSet/.