# V6072. Two similar code fragments were found. Perhaps, this is a typo and 'X' variable should be used instead of 'Y'.

The analyzer detected a code fragment probably containing a typo. It is very likely that this code was written by using the Copy-Paste technique.

The V6072 diagnostic looks for two adjacent code blocks similar in structure and different in one variable, which is used several times in the first block but only once in the second. This discrepancy suggests that the programmer forgot to change that variable to the proper one. The diagnostic is designed to detect situations where a code block is copied to make another block and the programmer forgets to change the names of some of the variables in the resulting block.

Consider the following example:

    if (x > 0)
    {
      Do1(x);
      Do2(x);
    }
    if (y > 0)
    {
      Do1(y);
      Do2(x); // <=
    }

In the second block, the programmer must have intended to use variable 'y', not 'x':

    if (x > 0)
    {
      Do1(x);
      Do2(x);
    }
    if (y > 0)
    {
      Do1(y);
      Do2(y);
    }

The following example is more complex.

    ....
    if(erendlinen>239) erendlinen=239;
    if(srendlinen>erendlinen) srendlinen=erendlinen;

    if(erendlinep>239) erendlinep=239;
    if(srendlinep>erendlinen) srendlinep=erendlinep;   // <=
    ....

The defect in this example is not that easy to see. The variables have similar names, which makes it much more difficult to diagnose the error. In the second block, variable 'erendlinep' should be used instead of 'erendlinen'.

This is what the fixed code should look like:

    ....
    if(erendlinen>239) erendlinen=239;
    if(srendlinen>erendlinen) srendlinen=erendlinen;

    if(erendlinep>239) erendlinep=239;
    if(srendlinep>erendlinep) srendlinep=erendlinep;   // <=
    ....

Obviously, 'erendlinen' and 'erendlinep' are poorly chosen variable names. An error like that is almost impossible to catch when carrying out code review. Even with the analyzer pointing at it directly, it is still not easy to notice. Therefore, take your time and make sure to examine the code closely when encountering a V6072 warning.

This diagnostic is classified as:

CWE-682

You can look at examples of errors detected by the V6072 diagnostic.