Contents
V6089. It's possible that the line was commented out improperly, thus altering the program's operation logics.
The analyzer has detected a potential error that has to do with altered execution logic due to inappropriate commenting-out of a code fragment.
This diagnostic rule looks for comments that look like regular code between the beginning of an 'if (...)' statement and its 'then' branch, with the latter having suspicious formatting. In this case, it is possible that the 'then' branch, in its current form, is a result of bad refactoring.
Consider the following example:
if (hwndTaskEdit == null)
// hwndTaskEdit = getTask(...);
if (hwndTaskEdit != null)
{
...
}The program no longer makes sense as the condition of the second 'if' statement will never be true.
Fixed version:
// if (hwndTaskEdit == null)
// hwndTaskEdit = getTask(...);
if (hwndTaskEdit != null)
{
...
}The analyzer doesn't generate the warning if code formatting meets the program's execution logic.
For example:
if (isReady)
// some comment
if (isSmt)
{
...
}This diagnostic is classified as:
|
Was this page helpful?
