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


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

I missed a bit of code.

Legend:

Unmodified
Added
Removed
Modified

  • Guidelines/Warnings/Microsoft

    v1 v2  
    66
    77 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.
     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.
    99 Suppression::
    1010    `#  pragma warning(disable: 4100) // 'name' : unreferenced formal parameter`