From: <bi...@us...> - 2013-12-09 23:41:45
|
Revision: 9662 http://sourceforge.net/p/oorexx/code-0/9662 Author: bigrixx Date: 2013-12-09 23:41:42 +0000 (Mon, 09 Dec 2013) Log Message: ----------- Fix error message file templates to generate publican-compatible error message files Modified Paths: -------------- docs/trunk/rexxref/en-US/errnums.xml docs/trunk/rexxref/en-US/errnumsrexxc.xml docs/trunk/rexxref/en-US/errnumsrxqueue.xml docs/trunk/rexxref/en-US/errnumssubcom.xml Modified: docs/trunk/rexxref/en-US/errnums.xml =================================================================== --- docs/trunk/rexxref/en-US/errnums.xml 2013-12-09 23:39:26 UTC (rev 9661) +++ docs/trunk/rexxref/en-US/errnums.xml 2013-12-09 23:41:42 UTC (rev 9662) @@ -242,14 +242,14 @@ <para> <emphasis role="bold">Explanation:</emphasis> </para> -<para>More ENDs were found in your program than DO or SELECT instructions, or the ENDs did not match the DO or SELECT instructions. This message also occurs if you try to transfer control into the middle of a loop using SIGNAL. In this case, the language processor does not expect the END because it did not process the previous DO instruction. Remember also that SIGNAL deactivates any current loops, so it cannot transfer control from one place inside a loop to another.</para> -<para>Another cause for this message is placing an END immediately after a THEN or ELSE subkeyword or specifying a name on the END keyword that does not match the name following DO. Putting the name of the control variable on ENDs that close repetitive loops can also help locate this kind of error.</para> +<para>More ENDs were found in your program than DO, LOOP, or SELECT instructions, or the ENDs did not match the DO, LOOP, or SELECT instructions. This message also occurs if you try to transfer control into the middle of a loop using SIGNAL. In this case, the language processor does not expect the END because it did not process the previous DO instruction. Remember also that SIGNAL deactivates any current loops, so it cannot transfer control from one place inside a loop to another.</para> +<para>Another cause for this message is placing an END immediately after a THEN or ELSE subkeyword or specifying a name on the END keyword that does not match the name following DO or LOOP. Putting the name of the control variable on ENDs that close repetitive loops can also help locate this kind of error.</para> <para>The associated subcodes are: </para> <variablelist> <varlistentry> <term>001</term> <listitem> -<para>END has no corresponding DO or SELECT</para> +<para>END has no corresponding DO, LOOP, or SELECT</para> </listitem> </varlistentry> <varlistentry> @@ -297,10 +297,10 @@ </para> <para>Your program exceeds the nesting level limit for control structures (for example, DO...END and IF...THEN...ELSE). This could be because of a looping INTERPRET instruction, such as:</para> <programlisting> - + line='INTERPRET line' INTERPRET line - + </programlisting> <para>These lines loop until they exceed the nesting level limit and the language processor issues this message. Similarly, a recursive subroutine or internal function that does not end correctly can loop until it causes this message.</para> <para>The associated subcodes are: </para> @@ -346,11 +346,11 @@ </variablelist> </section> <section id="ERR14"> -<title>Error 14 - Incomplete DO/SELECT/IF</title> +<title>Error 14 - Incomplete DO/LOOP/SELECT/IF</title> <para> <emphasis role="bold">Explanation:</emphasis> </para> -<para>At the end of the program or the string for an INTERPRET instruction, a DO or SELECT instruction was found without a matching END or an IF clause that is not followed by a THEN clause. Putting the name of the control variable on each END closing a controlled loop can help locate this kind of error.</para> +<para>At the end of the program or the string for an INTERPRET instruction, a DO, LOOP, or SELECT instruction was found without a matching END or an IF clause that is not followed by a THEN clause. Putting the name of the control variable on each END closing a controlled loop can help locate this kind of error.</para> <para>The associated subcodes are: </para> <variablelist> <varlistentry> @@ -378,6 +378,12 @@ </listitem> </varlistentry> <varlistentry> +<term>005</term> +<listitem> +<para>LOOP instruction on line <emphasis role="italic">line_number</emphasis> requires matching END</para> +</listitem> +</varlistentry> +<varlistentry> <term>901</term> <listitem> <para>OTHERWISE on line <emphasis role="italic">line_number</emphasis> requires matching END</para> @@ -392,19 +398,19 @@ </para> <para>Hexadecimal strings must not have leading or trailing whitespace characters and whitespace can only be embedded at byte boundaries. Only the digits 0-9 and the letters a-f and A-F are allowed. The following are valid hexadecimal strings: </para> <programlisting> - + '13'x 'A3C2 1c34'x '1de8'x - + </programlisting> <para>Binary strings can have whitespace only at the boundaries of groups of four binary digits. Only the digits 0 and 1 are allowed. These are valid binary strings: </para> <programlisting> - + '1011'b '110 1101'b '101101 11010011'b - + </programlisting> <para>You might have mistyped one of the digits, for example, typing a letter O instead of the number 0. Or you might have used the one-character symbol X or B (the name of the variable X or B, respectively) after a literal string when the string is not intended as a hexadecimal or binary specification. In this case, use the explicit concatenation operator (||) to concatenate the string to the value of the symbol.</para> <para>The associated subcodes are: </para> @@ -577,7 +583,7 @@ <varlistentry> <term>905</term> <listitem> -<para>String or symbol expected after EXTERNAL keyword</para> +<para>String expected after EXTERNAL keyword</para> </listitem> </varlistentry> <varlistentry> @@ -1151,6 +1157,12 @@ <para>Unknown keyword on ::OPTIONS directive; found "<emphasis role="italic">word</emphasis>"</para> </listitem> </varlistentry> +<varlistentry> +<term>925</term> +<listitem> +<para>Unknown keyword on ::ATTRIBUTE directive; found "<emphasis role="italic">word</emphasis>"</para> +</listitem> +</varlistentry> </variablelist> </section> <section id="ERR26"> @@ -2816,7 +2828,7 @@ <varlistentry> <term>901</term> <listitem> -<para>Not enough arguments in method; <emphasis role="italic">number</emphasis> expected</para> +<para>Not enough arguments for method; <emphasis role="italic">number</emphasis> expected</para> </listitem> </varlistentry> <varlistentry> @@ -3667,7 +3679,54 @@ <para>Duplicate ::CONSTANT directive instruction</para> </listitem> </varlistentry> +<varlistentry> +<term>933</term> +<listitem> +<para>Abstract methods cannot have a method body</para> +</listitem> +</varlistentry> +<varlistentry> +<term>934</term> +<listitem> +<para>Attribute methods cannot have a method body</para> +</listitem> +</varlistentry> +<varlistentry> +<term>935</term> +<listitem> +<para>External attributes cannot have a method body</para> +</listitem> +</varlistentry> +<varlistentry> +<term>936</term> +<listitem> +<para>External methods cannot have a method body</para> +</listitem> +</varlistentry> +<varlistentry> +<term>937</term> +<listitem> +<para>Attribute methods without a SET or GET designation cannot have a method body</para> +</listitem> +</varlistentry> +<varlistentry> +<term>938</term> +<listitem> +<para>Constant methods cannot have a method body</para> +</listitem> +</varlistentry> +<varlistentry> +<term>939</term> +<listitem> +<para>External routines cannot have a method body</para> +</listitem> +</varlistentry> +<varlistentry> +<term>940</term> +<listitem> +<para>Abstract attributes cannot have a method body</para> +</listitem> +</varlistentry> </variablelist> </section> </section> - Modified: docs/trunk/rexxref/en-US/errnumsrexxc.xml =================================================================== --- docs/trunk/rexxref/en-US/errnumsrexxc.xml 2013-12-09 23:39:26 UTC (rev 9661) +++ docs/trunk/rexxref/en-US/errnumsrexxc.xml 2013-12-09 23:41:42 UTC (rev 9662) @@ -1,4 +1,3 @@ - <section id="rexxcup"> <title>RexxC Utility Program</title> <para>When RexxC encounters a syntax error in a Rexx program while tokenizing or syntax checking it, RexxC Modified: docs/trunk/rexxref/en-US/errnumsrxqueue.xml =================================================================== --- docs/trunk/rexxref/en-US/errnumsrxqueue.xml 2013-12-09 23:39:26 UTC (rev 9661) +++ docs/trunk/rexxref/en-US/errnumsrxqueue.xml 2013-12-09 23:41:42 UTC (rev 9662) @@ -1,4 +1,3 @@ - <section id="rxqueueup"> <title>RXQUEUE Utility Program</title> <para>RXQUEUE issues the following errors:</para> @@ -31,9 +30,9 @@ <para>The queue name contains an invalid character. Only the following characters can appear in queue names: </para> <programlisting> - + 'A' .. 'Z', '0' .. '9', '.', '!', '?', '_' - + </programlisting> </section> <section id="ERR123"> Modified: docs/trunk/rexxref/en-US/errnumssubcom.xml =================================================================== --- docs/trunk/rexxref/en-US/errnumssubcom.xml 2013-12-09 23:39:26 UTC (rev 9661) +++ docs/trunk/rexxref/en-US/errnumssubcom.xml 2013-12-09 23:41:42 UTC (rev 9662) @@ -1,4 +1,3 @@ - <section id="rxsubcomup"> <title>RXSUBCOM Utility Program</title> <para>RXSUBCOM issues the following errors:</para> |