COMPERR parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
No edit summary
Line 15: Line 15:
You can choose the volume of compiler errors you want returned to you and how you want them displayed, so you can locate the problem more easily.
You can choose the volume of compiler errors you want returned to you and how you want them displayed, so you can locate the problem more easily.


The following table shows the effect on the error messages when any the corresponding <var>COMPERR</var> bit is on:
The following table shows the effect on compilation error messages when the corresponding <var>COMPERR</var> bit is on:


<table class="thJustBold">
<table class="thJustBold">
<tr class="head"><th>Bit</th><th>Effect</th></tr>
<tr><th>Bit</th><th>Effect</th></tr>


<tr><td>X'01'</td><td>Insert <code>&lt;&lt;</code> and <code>>></code> characters around the token at or near the source of the error, helping you to locate it in the echo of the line in which the error was detected.</td></tr>
<tr><td>X'01'</td><td>The echo of the line in error has <code>&lt;&lt;</code> and <code>>></code> characters around the token which is at or near the error.</td></tr>


<tr><td>X'02'</td><td>After echoing the line in which the error was detected, insert a line that contains hyphens (<code>---</code>) beneath the token at or near the source of the error, helping you to locate it in the echoed line.
<tr><td>X'02'</td><td>The echo of the line in error is followed by a line containing hyphens (<code>---</code>) beneath the token which is at or near the error.


<tr><td>X'04'</td><td>Allow the compiler to continue processing a line even after an error has been detected on it.  If this bit is <b>not</b> set, only the first error is displayed. <p>Mutliple error messages for a single line are most often "noise" caused by cascading errors, so suppressing multiple error messages (that is, <b>not</b> setting X'04') may make it easier for you to identify the errors in the <var class="product">SOUL</var> request.</p></td></tr>
<tr><td>X'04'</td><td>Allow the compiler to continue processing a line even after an error has been detected in it.  If this bit is <b>not</b> set, only the first error is displayed for any line. <p>Mutliple error messages for a single line are most often "noise" caused by cascading errors, so suppressing multiple error messages (that is, <b>not</b> setting X'04') may make it easier for you to identify the errors in the <var class="product">SOUL</var> request.</p></td></tr>
</table>
</table>
[[Category:User parameters]]
[[Category:User parameters]]
[[Category:Parameters]]
[[Category:Parameters]]

Revision as of 00:57, 11 June 2013

Summary

Default value
X'04'
Parameter type
User
Where set
In CCAIN User 0 parameters
Related products
All
Introduced
Model 204 V7.4

Description

You can choose the volume of compiler errors you want returned to you and how you want them displayed, so you can locate the problem more easily.

The following table shows the effect on compilation error messages when the corresponding COMPERR bit is on:

BitEffect
X'01'The echo of the line in error has << and >> characters around the token which is at or near the error.
X'02'The echo of the line in error is followed by a line containing hyphens (---) beneath the token which is at or near the error.
X'04'Allow the compiler to continue processing a line even after an error has been detected in it. If this bit is not set, only the first error is displayed for any line.

Mutliple error messages for a single line are most often "noise" caused by cascading errors, so suppressing multiple error messages (that is, not setting X'04') may make it easier for you to identify the errors in the SOUL request.