- </td>
- </tr>
- </table>
-
- <p><span class="emphasis"><i class="EMPHASIS">Note:</i></span> If you
- already have a default condition, you are obviously exempt from this
- point. Of note, most of the WIN32 code calls `DefWindowProc' after
- the switch statement. This API call *should* be included in a default
- statement.</p>
-
- <p><span class="emphasis"><i class="EMPHASIS">Another
- Note:</i></span> This is not so much a readability issue as a robust
- programming issue. The "anomaly code goes here" may be no more than a
- print to the STDERR stream (as in load_config). Or it may really be
- an abort condition.</p>
-
- <p><span class="emphasis"><i class="EMPHASIS">Status:</i></span>
- Programmer discretion is advised.</p>
- </div>
-
- <div class="SECT3">
- <h3 class="SECT3"><a name="S38" id="S38">4.7.3. Try to avoid falling
- through cases in a switch statement.</a></h3>
-
- <p><span class="emphasis"><i class=
- "EMPHASIS">Explanation:</i></span></p>
-
- <p>In general, you will want to have a 'break' statement within each
- 'case' of a switch statement. This allows for the code to be more
- readable and understandable, and furthermore can prevent unwanted
- surprises if someone else later gets creative and moves the code
- around.</p>
-
- <p>The language allows you to plan the fall through from one case
- statement to another simply by omitting the break statement within
- the case statement. This feature does have benefits, but should only
- be used in rare cases. In general, use a break statement for each
- case statement.</p>
-
- <p>If you choose to allow fall through, you should comment both the
- fact of the fall through and reason why you felt it was
- necessary.</p>
- </div>
-
- <div class="SECT3">
- <h3 class="SECT3"><a name="S39" id="S39">4.7.4. Use 'long' or 'short'
- Instead of 'int'</a></h3>
-
- <p><span class="emphasis"><i class=
- "EMPHASIS">Explanation:</i></span></p>
-
- <p>On 32-bit platforms, int usually has the range of long. On 16-bit
- platforms, int has the range of short.</p>
-
- <p><span class="emphasis"><i class="EMPHASIS">Status:</i></span>
- open-to-debate. In the case of most FSF projects (including
- X/GNU-Emacs), there are typedefs to int4, int8, int16, (or
- equivalence ... I forget the exact typedefs now). Should we add these
- to IJB now that we have a "configure" script?</p>
- </div>
-
- <div class="SECT3">
- <h3 class="SECT3"><a name="S40" id="S40">4.7.5. Don't mix size_t and
- other types</a></h3>
-
- <p><span class="emphasis"><i class=
- "EMPHASIS">Explanation:</i></span></p>
-
- <p>The type of size_t varies across platforms. Do not make
- assumptions about whether it is signed or unsigned, or about how long
- it is. Do not compare a size_t against another variable of a
- different type (or even against a constant) without casting one of
- the values.</p>
- </div>
-
- <div class="SECT3">
- <h3 class="SECT3"><a name="S41" id="S41">4.7.6. Declare each variable
- and struct on its own line.</a></h3>
-
- <p><span class="emphasis"><i class=
- "EMPHASIS">Explanation:</i></span></p>
-
- <p>It can be tempting to declare a series of variables all on one
- line. Don't.</p>
-
- <p><span class="emphasis"><i class="EMPHASIS">Example:</i></span></p>
-
- <table border="0" bgcolor="#E0E0E0" width="100%">
- <tr>
- <td>
- <pre class="PROGRAMLISTING">
+ </td>
+ </tr>
+ </table>
+ <p>
+ <span class="emphasis"><i class="EMPHASIS">Note:</i></span> If
+ you already have a default condition, you are obviously exempt
+ from this point. Of note, most of the WIN32 code calls
+ `DefWindowProc' after the switch statement. This API call
+ *should* be included in a default statement.
+ </p>
+ <p>
+ <span class="emphasis"><i class="EMPHASIS">Another
+ Note:</i></span> This is not so much a readability issue as a
+ robust programming issue. The "anomaly code goes here" may be no
+ more than a print to the STDERR stream (as in load_config). Or it
+ may really be an abort condition.
+ </p>
+ <p>
+ <span class="emphasis"><i class="EMPHASIS">Status:</i></span>
+ Programmer discretion is advised.
+ </p>
+ </div>
+ <div class="SECT3">
+ <h3 class="SECT3">
+ <a name="S38">4.7.3. Try to avoid falling through cases in a
+ switch statement.</a>
+ </h3>
+ <p>
+ <span class="emphasis"><i class=
+ "EMPHASIS">Explanation:</i></span>
+ </p>
+ <p>
+ In general, you will want to have a 'break' statement within each
+ 'case' of a switch statement. This allows for the code to be more
+ readable and understandable, and furthermore can prevent unwanted
+ surprises if someone else later gets creative and moves the code
+ around.
+ </p>
+ <p>
+ The language allows you to plan the fall through from one case
+ statement to another simply by omitting the break statement
+ within the case statement. This feature does have benefits, but
+ should only be used in rare cases. In general, use a break
+ statement for each case statement.
+ </p>
+ <p>
+ If you choose to allow fall through, you should comment both the
+ fact of the fall through and reason why you felt it was
+ necessary.
+ </p>
+ </div>
+ <div class="SECT3">
+ <h3 class="SECT3">
+ <a name="S40">4.7.4. Don't mix size_t and other types</a>
+ </h3>
+ <p>
+ <span class="emphasis"><i class=
+ "EMPHASIS">Explanation:</i></span>
+ </p>
+ <p>
+ The type of size_t varies across platforms. Do not make
+ assumptions about whether it is signed or unsigned, or about how
+ long it is. Do not compare a size_t against another variable of a
+ different type (or even against a constant) without casting one
+ of the values.
+ </p>
+ </div>
+ <div class="SECT3">
+ <h3 class="SECT3">
+ <a name="S41">4.7.5. Declare each variable and struct on its own
+ line.</a>
+ </h3>
+ <p>
+ <span class="emphasis"><i class=
+ "EMPHASIS">Explanation:</i></span>
+ </p>
+ <p>
+ It can be tempting to declare a series of variables all on one
+ line. Don't.
+ </p>
+ <p>
+ <span class="emphasis"><i class="EMPHASIS">Example:</i></span>
+ </p>
+ <table border="0" bgcolor="#E0E0E0" width="100%">
+ <tr>
+ <td>
+<pre class="PROGRAMLISTING">