Q64828: Why Some Sample Programs Produce Compiler Warnings

Article: Q64828
Product(s): See article
Version(s): 6.00   | 6.00
Operating System(s): MS-DOS | OS/2
Keyword(s): ENDUSER | s_quickc s_pascal | mspl13_c
Last Modified: 15-AUG-1990

The following list outlines reasons why the sample programs included
with many Microsoft language products might produce warnings when
compiled:

1. Many of the language elements (for instance, typecasts), which
   might be necessary to eliminate the warnings, could obscure the
   points the writer is trying to emphasize.

   The sample programs are included to explain a topic or demonstrate
   how to use a feature, and might not necessarily reflect model
   programming practice.

2. The documents are written well before the compiler is finished in
   the development process. The warnings sometimes change as the
   compiler progresses. Therefore, it is very difficult to write
   warning-free code early in the development process and have it
   compile with no warnings with the release version.

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1986-2002.