Changes between Initial Version and Version 1 of Guidelines/Warnings/Microsoft


Ignore:
Timestamp:
Sep 2, 2010, 10:25:41 PM (12 years ago)
Author:
Daniel James
Comment:

Demo of how microsoft warnings could be laid out.

Legend:

Unmodified
Added
Removed
Modified
  • Guidelines/Warnings/Microsoft

    v1 v1  
     1= Microsoft Warnings =
     2
     3[[PageOutline]]
     4
     5== C4100 - Unreferenced formal parameter == #c4100
     6
     7 Suggestion::
     8    Either surround the parameter with C comments, for example: `int /* my_variable */`) or just delete if the variable name is uninformative. If in other's module(s), or you are too busy/idle, at least suppress warning. In generic code you might not be able to comment the variable name as it might actually be used to call a static function. In this case simply referencing the variable (varname;) in the function body eliminates the warning.
     9 Suppression::
     10    `#  pragma warning(disable: 4100) // 'name' : unreferenced formal parameter`
     11
     12== C4127 - Conditional expression is constant == #c4127
     13
     14 Suggestion::
     15    Very common and many believe unhelpful, but a few find it informative, so do not suppress globally.  Even `while(true)` can trigger this! `while(true)` can be rewritten as `for(;;)` eliminating the warning.
     16 Suppression::
     17    `#  pragma warning(disable: 4127) // conditional expression is constant.`