From e4f8b6fef03e0c0877b5e953712fc0fb58cef487 Mon Sep 17 00:00:00 2001 From: Greg King Date: Thu, 24 Apr 2014 13:03:52 -0400 Subject: [PATCH 1/3] Avoided makeinfo warnings when Travis CI runs LinuxDoc Tools. --- doc/ca65.sgml | 8 ++++---- doc/funcref.sgml | 30 +++++++++++++++--------------- doc/intro.sgml | 6 +++--- 3 files changed, 22 insertions(+), 22 deletions(-) diff --git a/doc/ca65.sgml b/doc/ca65.sgml index caf022c16..543370fd1 100644 --- a/doc/ca65.sgml +++ b/doc/ca65.sgml @@ -3,7 +3,7 @@
ca65 Users Guide <author><url url="mailto:uz@cc65.org" name="Ullrich von Bassewitz"> -<date>2014-04-10 +<date>2014-04-24 <abstract> ca65 is a powerful macro assembler for the 6502, 65C02 and 65816 CPUs. It is @@ -814,7 +814,7 @@ to find branch targets (this is the reason why I for my part do prefer the "cheap" local labels). Nevertheless, unnamed labels are convenient in some situations, so it's your decision. -<bf/Note:/ <ref id="scopes" name="Scopes"> organize named symbols, not +<em/Note:/ <ref id="scopes" name="Scopes"> organize named symbols, not unnamed ones, so scopes don't have an effect on unnamed labels. @@ -984,7 +984,7 @@ is actually the same as This is the reason why a procedure must have a name. If you want a scope without a name, use <tt/<ref id=".SCOPE" name=".SCOPE">/. -<bf/Note:/ As you can see from the example above, scopes and symbols live in +<em/Note:/ As you can see from the example above, scopes and symbols live in different namespaces. There can be a symbol named <tt/foo/ and a scope named <tt/foo/ without any conflicts (but see the section titled <ref id="scopesearch" name=""Scope search order"">). @@ -2665,7 +2665,7 @@ Here's a list of all control commands and a description, what they do: <tscreen><verb> lda #'a </verb></tscreen> - <bf/Note:/ This does not work in conjunction with <tt/.FEATURE + <em/Note:/ This does not work in conjunction with <tt/.FEATURE loose_string_term/, since in this case the input would be ambiguous. <tag><tt>org_per_seg</tt><label id="org_per_seg"></tag> diff --git a/doc/funcref.sgml b/doc/funcref.sgml index adfeaf4b2..7ab8c2d14 100644 --- a/doc/funcref.sgml +++ b/doc/funcref.sgml @@ -3,7 +3,7 @@ <article> <title>cc65 function reference <author><url url="mailto:uz@cc65.org" name="Ullrich von Bassewitz"> -<date>2014-04-10 +<date>2014-04-24 <abstract> cc65 is a C compiler for 6502 based systems. This function reference describes @@ -26,7 +26,7 @@ For an overview about the available libraries, their purpose, and any differences to the ISO standard, please have a look at the <url url="library.html" name="cc65 Library Overview">. -<bf/Note:/ Standard C functions are listed here, but not described in detail. +<em/Note:/ Standard C functions are listed here, but not described in detail. Since these functions behave identical on all standard compliant systems, they are described in any book covering standard C. @@ -3194,7 +3194,7 @@ else. <tag/Limits/<itemize> <item>When compiling with <tt/-Os/ the function is actually a macro. The inline sequence generated by the macro will not work correctly for values -outside the range 0..255. <bf/Note:/ The constant <tt/EOF/ is not part of +outside the range 0..255. <em/Note:/ The constant <tt/EOF/ is not part of this range. The non inline function may be accessed by <tt/#undef/'ing the macro. <item>When compiling without <tt/-Os/, the function is only available as @@ -3231,7 +3231,7 @@ is a letter. The return value is zero if the character is anything else. <tag/Limits/<itemize> <item>When compiling with <tt/-Os/ the function is actually a macro. The inline sequence generated by the macro will not work correctly for values -outside the range 0..255. <bf/Note:/ The constant <tt/EOF/ is not part of +outside the range 0..255. <em/Note:/ The constant <tt/EOF/ is not part of this range. The non inline function may be accessed by <tt/#undef/'ing the macro. <item>When compiling without <tt/-Os/, the function is only available as @@ -3268,7 +3268,7 @@ is in the range 0..127 (the range of valid ASCII characters) and zero if not. <tag/Limits/<itemize> <item>When compiling with <tt/-Os/ the function is actually a macro. The inline sequence generated by the macro will not work correctly for values -outside the range 0..255. <bf/Note:/ The constant <tt/EOF/ is not part of +outside the range 0..255. <em/Note:/ The constant <tt/EOF/ is not part of this range. The non inline function may be accessed by <tt/#undef/'ing the macro. <item>When compiling without <tt/-Os/, the function is only available as @@ -3306,7 +3306,7 @@ anything else. <tag/Limits/<itemize> <item>When compiling with <tt/-Os/ the function is actually a macro. The inline sequence generated by the macro will not work correctly for values -outside the range 0..255. <bf/Note:/ The constant <tt/EOF/ is not part of +outside the range 0..255. <em/Note:/ The constant <tt/EOF/ is not part of this range. The non inline function may be accessed by <tt/#undef/'ing the macro. <item>When compiling without <tt/-Os/, the function is only available as @@ -3344,7 +3344,7 @@ else. <tag/Limits/<itemize> <item>When compiling with <tt/-Os/ the function is actually a macro. The inline sequence generated by the macro will not work correctly for values -outside the range 0..255. <bf/Note:/ The constant <tt/EOF/ is not part of +outside the range 0..255. <em/Note:/ The constant <tt/EOF/ is not part of this range. The non inline function may be accessed by <tt/#undef/'ing the macro. <item>When compiling without <tt/-Os/, the function is only available as @@ -3381,7 +3381,7 @@ is a digit. The return value is zero if the character is anything else. <tag/Limits/<itemize> <item>When compiling with <tt/-Os/ the function is actually a macro. The inline sequence generated by the macro will not work correctly for values -outside the range 0..255. <bf/Note:/ The constant <tt/EOF/ is not part of +outside the range 0..255. <em/Note:/ The constant <tt/EOF/ is not part of this range. The non inline function may be accessed by <tt/#undef/'ing the macro. <item>When compiling without <tt/-Os/, the function is only available as @@ -3420,7 +3420,7 @@ if the character is anything else. <tag/Limits/<itemize> <item>When compiling with <tt/-Os/ the function is actually a macro. The inline sequence generated by the macro will not work correctly for values -outside the range 0..255. <bf/Note:/ The constant <tt/EOF/ is not part of +outside the range 0..255. <em/Note:/ The constant <tt/EOF/ is not part of this range. The non inline function may be accessed by <tt/#undef/'ing the macro. <item>When compiling without <tt/-Os/, the function is only available as @@ -3458,7 +3458,7 @@ else. <tag/Limits/<itemize> <item>When compiling with <tt/-Os/ the function is actually a macro. The inline sequence generated by the macro will not work correctly for values -outside the range 0..255. <bf/Note:/ The constant <tt/EOF/ is not part of +outside the range 0..255. <em/Note:/ The constant <tt/EOF/ is not part of this range. The non inline function may be accessed by <tt/#undef/'ing the macro. <item>When compiling without <tt/-Os/, the function is only available as @@ -3496,7 +3496,7 @@ is zero if the character is anything else. <tag/Limits/<itemize> <item>When compiling with <tt/-Os/ the function is actually a macro. The inline sequence generated by the macro will not work correctly for values -outside the range 0..255. <bf/Note:/ The constant <tt/EOF/ is not part of +outside the range 0..255. <em/Note:/ The constant <tt/EOF/ is not part of this range. The non inline function may be accessed by <tt/#undef/'ing the macro. <item>When compiling without <tt/-Os/, the function is only available as @@ -3535,7 +3535,7 @@ value is zero if the character is anything else. <tag/Limits/<itemize> <item>When compiling with <tt/-Os/ the function is actually a macro. The inline sequence generated by the macro will not work correctly for values -outside the range 0..255. <bf/Note:/ The constant <tt/EOF/ is not part of +outside the range 0..255. <em/Note:/ The constant <tt/EOF/ is not part of this range. The non inline function may be accessed by <tt/#undef/'ing the macro. <item>When compiling without <tt/-Os/, the function is only available as @@ -3575,7 +3575,7 @@ newline ('\n'), carriage return ('\r'), horizontal tab ('\t'), and vertical tab <tag/Limits/<itemize> <item>When compiling with <tt/-Os/ the function is actually a macro. The inline sequence generated by the macro will not work correctly for values -outside the range 0..255. <bf/Note:/ The constant <tt/EOF/ is not part of +outside the range 0..255. <em/Note:/ The constant <tt/EOF/ is not part of this range. The non inline function may be accessed by <tt/#undef/'ing the macro. <item>When compiling without <tt/-Os/, the function is only available as @@ -3613,7 +3613,7 @@ else. <tag/Limits/<itemize> <item>When compiling with <tt/-Os/ the function is actually a macro. The inline sequence generated by the macro will not work correctly for values -outside the range 0..255. <bf/Note:/ The constant <tt/EOF/ is not part of +outside the range 0..255. <em/Note:/ The constant <tt/EOF/ is not part of this range. The non inline function may be accessed by <tt/#undef/'ing the macro. <item>When compiling without <tt/-Os/, the function is only available as @@ -3651,7 +3651,7 @@ character is anything else. <tag/Limits/<itemize> <item>When compiling with <tt/-Os/ the function is actually a macro. The inline sequence generated by the macro will not work correctly for values -outside the range 0..255. <bf/Note:/ The constant <tt/EOF/ is not part of +outside the range 0..255. <em/Note:/ The constant <tt/EOF/ is not part of this range. The non inline function may be accessed by <tt/#undef/'ing the macro. <item>When compiling without <tt/-Os/, the function is only available as diff --git a/doc/intro.sgml b/doc/intro.sgml index d9f6c863a..02c5c83d5 100644 --- a/doc/intro.sgml +++ b/doc/intro.sgml @@ -7,7 +7,7 @@ <url url="mailto:uz@cc65.org" name="Ullrich von Bassewitz">,<newline> <url url="mailto:cbmnut@hushmail.com" name="CbmNut">,<newline> <url url="mailto:greg.king5@verizon.net" name="Greg King"> -<date>2005-7-22 +<date>2014-4-24 <abstract> How to use the cc65 C language system -- an introduction. @@ -40,7 +40,7 @@ files and unpack all three into one directory. In case of the .ZIP archives, you will also need to set the environment variables <tt/CC65_INC/, <tt/LD65_LIB/ and <tt/LD65_CFG/ as described below. -<bf/Note/: There is a much simpler way to compile this example, by using the +<em/Note:/ There is a much simpler way to compile this example, by using the <bf/cl65/ compile-and-link utility. However, it makes sense to understand how the separate steps work. How to do the example with the <bf/cl65/ utility is described <ref id="using-cl65" name="later">. @@ -330,7 +330,7 @@ disks/, and set the path of <bf/H1:/ to your executables directory, then use "<bf/H0:HELLO.XEX/" in the above procedure (after pressing <tt/L/), to access your harddrive directly. -<bf/Note/: There is no delay after the program exits, as you are returned +<em/Note:/ There is no delay after the program exits, as you are returned to the DOS menu. Your C program should wait for a keypress if you want to see any output. From d2bb12d17acb7414def7b0bb9f35940d171ab921 Mon Sep 17 00:00:00 2001 From: Greg King <gregdk@users.sf.net> Date: Fri, 25 Apr 2014 03:33:53 -0400 Subject: [PATCH 2/3] Avoided some makeinfo warnings when Cygwin runs LinuxDoc Tools. --- doc/atari.sgml | 4 +--- doc/grc65.sgml | 4 ++-- doc/smc.sgml | 9 +++------ 3 files changed, 6 insertions(+), 11 deletions(-) diff --git a/doc/atari.sgml b/doc/atari.sgml index 64a28c7b5..47ce050e1 100644 --- a/doc/atari.sgml +++ b/doc/atari.sgml @@ -6,7 +6,7 @@ <author> <url url="mailto:shawnjefferson@24fightingchickens.com" name="Shawn Jefferson"> and<newline> <url url="mailto:chris@groessler.org" name="Christian Groessler"> -<date>2014-04-10 +<date>2014-04-24 <abstract> An overview over the Atari runtime system as it is implemented for the cc65 C @@ -435,7 +435,6 @@ Currently there are two joystick drivers available: <tt/atrstd.joy (atrstd_joy)/|<tt/atrxstd.joy (atrxstd_joy)/|Supports up to two/four standard joysticks connected to the joystick ports of the Atari. (Four on the pre-XL systems, two on XL or newer.)@ <tt/atrmj8.joy (atrmj8_joy)/|<tt/atrxmj8.joy (atrxmj8_joy)/|Supports up to eight standard joysticks connected to a MultiJoy adapter. </tabular> -<caption> </table> Default drivers: <tt/atrstd.joy (atrstd_joy)/ and <tt/atrxstd.joy (atrxstd_joy)/. @@ -453,7 +452,6 @@ Currently there are five mouse drivers available: <tt/atrtrk.mou (atrtrk_mou)/|<tt/atrxtrk.mou (atrxtrk_mou)/|Supports an Atari trakball.@ <tt/atrtt.mou (atrtt_mou)/|<tt/atrxtt.mou (atrxtt_mou)/|Supports an Atari touch tablet. </tabular> -<caption> </table> All mouse devices connect to joystick port #0. diff --git a/doc/grc65.sgml b/doc/grc65.sgml index 49d3f6798..1acc6b1f2 100644 --- a/doc/grc65.sgml +++ b/doc/grc65.sgml @@ -7,7 +7,7 @@ <author> <url url="mailto:ytm@elysium.pl" name="Maciej 'YTM/Elysium' Witkowiak">,<newline> <url url="mailto:greg.king5@verizon.net" name="Greg King"> -<date>VII 2000; VI,VII 2002; 2005-8-3 +<date>2014-04-24 <abstract> This document describes a compiler that can create GEOS headers and menues for cc65-compiled programs. @@ -344,7 +344,7 @@ for addresses. -<appendix> +<!-- <appendix> --> <sect>Appendix A -- example.grc<label id="example-grc"> <p><tscreen><verb> ; Note that MENU can define both menues and submenues. diff --git a/doc/smc.sgml b/doc/smc.sgml index b58fc51ab..240c78e7b 100644 --- a/doc/smc.sgml +++ b/doc/smc.sgml @@ -3,7 +3,7 @@ <article> <title>ca65 Macros for Self Modifying Code <author>Christian Krüger -<date>2012-02-19 +<date>2014-04-24 <abstract> The 'smc.inc' macro package for ca65 eases the use, increases the safeness and @@ -546,9 +546,8 @@ Let's have a look on a quite sophisticated example for the usage of SMC. It not only modifies code, but also the modification of the code is modified - allowing reuse of some instructions. -The code is from my 'memset()'implementation: - <descrip> +<tag/The code is from my 'memset()'implementation:/ <tscreen><verb> 1: ... 2: SMC_StoreAddress StoreAccuFirstSection @@ -568,8 +567,7 @@ The code is from my 'memset()'implementation: 16: ... </verb></tscreen> -Some explanation: - +<tag/Some explanation:/ Line 2: The register pair A/X contains an address, which is stored on the address location of a SMC line called 'StoreAccuFirstSection'. According to cc65's calling convention, the low-byte is in accu while the high-byte is in @@ -593,4 +591,3 @@ changed in the future... Line 14,15: The original code from line 8 is reestablished. </descrip> </article> - From f7f206958794368d45523ed265757706efa7365c Mon Sep 17 00:00:00 2001 From: Greg King <gregdk@users.sf.net> Date: Thu, 24 Apr 2014 13:03:52 -0400 Subject: [PATCH 3/3] Avoided makeinfo warnings when Travis CI runs LinuxDoc Tools. --- doc/cbm510.sgml | 4 ++-- doc/cbm610.sgml | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/cbm510.sgml b/doc/cbm510.sgml index 3d01ab5bb..c24eba142 100644 --- a/doc/cbm510.sgml +++ b/doc/cbm510.sgml @@ -7,7 +7,7 @@ <url url="mailto:uz@cc65.org" name="Ullrich von Bassewitz">,<newline> <url url="mailto:polluks@sdf.lonestar.org" name="Stefan A. Haubenthal">,<newline> <url url="mailto:greg.king5@verizon.net" name="Greg King"> -<date>2014-04-02 +<date>2014-04-25 <abstract> An overview over the Commodore 510 runtime system as it is implemented for the @@ -136,7 +136,7 @@ The following pseudo variables declared in the <tt/cbm510.h/ header file do allow access to hardware located in the address space. Some variables are structures; accessing the struct fields will access the chip registers. -<bf>Note:</bf> All I/O chips are located in the system bank (bank 15); and can +<em/Note:/ All I/O chips are located in the system bank (bank 15); and can therefore not be accessed like on other platforms. Please use one of the <tt/peekbsys/, <tt/peekwsys/, <tt/pokebsys/, and <tt/pokewsys/ functions to access the I/O chips. Direct reads and writes to the structures named below diff --git a/doc/cbm610.sgml b/doc/cbm610.sgml index 2025c0792..790983b3d 100644 --- a/doc/cbm610.sgml +++ b/doc/cbm610.sgml @@ -6,7 +6,7 @@ <author> <url url="mailto:uz@cc65.org" name="Ullrich von Bassewitz">,<newline> <url url="mailto:greg.king5@verizon.net" name="Greg King"> -<date>2014-04-02 +<date>2014-04-25 <abstract> An overview over the Commodore 610 runtime system as it is implemented for the @@ -138,7 +138,7 @@ The following pseudo variables declared in the <tt/cbm610.h/ header file do allow access to hardware located in the address space. Some variables are structures; accessing the struct fields will access the chip registers. -<bf>Note:</bf> All I/O chips are located in the system bank (bank 15); and can +<em/Note:/ All I/O chips are located in the system bank (bank 15); and can therefore not be accessed like on other platforms. Please use one of the <tt/peekbsys/, <tt/peekwsys/, <tt/pokebsys/, and <tt/pokewsys/ functions to access the I/O chips. Direct reads and writes to the structures named below