In some situations, after code refactoring, parts of the old constructs may remain. They are correctly accepted by the compiler, but can critically affect program execution. For example, if you switch from `do {...} while ();` to `while () {...}` forgetting to remove the old construct completely, you get `while(){...}while();` which may be vulnerable. These code snippets look suspicious and require the developer's attention.
+ + +We recommend that you use more explicit code transformations.
+ +The following example demonstrates the erroneous and corrected sections of the code.
+Using bitwise operations can be a mistake in some situations. For example, if parameters are evaluated in an expression and the function should be called only upon certain test results. These bitwise operations look suspicious and require developer attention.
+ + +We recommend that you evaluate the correctness of using the specified bit operations.
+ +The following example demonstrates the erroneous and fixed use of bit and logical operations.
+Finding places of confusing use of boolean type. For example, a unary minus does not work before a boolean type and an increment always gives true.
+ + +we recommend making the code simpler.
+ +The following example demonstrates erroneous and fixed methods for using a boolean data type.
+