Consider inspecting the loop expression. Function receives suspicious argument. A function should have a single point of exit at the end. The line contains control character 0x0B (vertical tabulation). Suspicious function declaration. Consider assigning event to a local variable before invoking it. Exception caught by handler for base class. V6069. It is possible that an error is present. The 'malloc' function allocates suspicious amount of memory calculated by 'strlen(expr)'. MISRA. AUTOSAR. V828. Consider pre-allocating it by calling reserve(N). V111. Comparison of arrays, strings, collections by reference. Constructor has the same name as that of the class. V595. , , , . V2543. It is pointless to compute the distance between the elements of different arrays. AUTOSAR. MISRA. Two or more case-branches perform the same actions. Some of the references in project are missing or incorrect. V6068. , 3.Destructor has the same name as the first member function of the class., 4. V669.

V2534. V518. V3046. Decreased performance. V2602. What is the difference between pure virtual and absult virtual class. MISRA. Consider inspecting 'X'. If the programmer does not explicitly provide a destructor, then which of the following creates an empty destructor? Consider inspecting the expression. Probably it is a mistake. :' operator, regardless of its conditional expression, always returns the same value. , , . V1016. Exception classes should be publicly accessible. V3175. Attempt to free memory containing the 'int A[10]' array by using the 'free(A)' function. The 'X' counter is not used inside a nested loop. Which is used to make a copy of one class object from another class object of the same class type. V121. The expression contains a suspicious mix of integer and real types. Waiting on this expression is unreliable, as compiler may optimize some of the variables. The left operand of integer division is less than the right one. V634. Incorrect comparison of BOOL type variable with TRUE. V6042. An object is used as an argument to its own method. Perhaps, this is a typo and 'X' variable should be used instead of 'Y'. The expression is excessive or contains a misprint. V1025. Consider inspecting the expression. V574. Variable is used after it is moved. MISRA. > ? V737. Argument is of the 'T' type. V2518. The signature of method 'X' does not conform to serialization requirements. V3502. The field (property) is used before it is initialized in constructor. V1024. An abnormality within similar comparisons. The 'foo' local variable has the same name as one of class members. V3042. ConcurrentModificationException may occur.

V1029. The first 'if' statement contains method return. Pointer is dereferenced on the initialization list before its check for null inside the body of a constructor function. V2605. The expression is checked for compatibility with the type 'A', but is casted to the 'B' type. Strings were concatenated but not used. The 'zero' value is assigned to pointer.

V3118. Silent suppression of exceptions can hide the presence of bugs in source code during testing. V002. V646. > ? Pointer was used before its check for nullptr. > ? :' operator uses constants from different enums.

>. V6029. V3148. Pointer to FILE should not be dereferenced. Suspicious return of a local reference variable which always equals null. V015. Some warnings could have been disabled. V202. V628. > ? V2619. Make sure the expression is correct. A switch-label should only appear at the top level of the compound statement forming the body of a 'switch' statement. Conversions between pointers to objects and integer types should not be performed. A pointer/reference parameter in a function should be declared as pointer/reference to const if the corresponding object was not modified. Consider inspecting the 'for' operator. V207. Possible LDAP injection. Passing objects of incompatible types to the method of collection. Storing credentials inside source code can lead to security issues. V2578. V3060. The '&' or '|' operator is applied to bool type value. An overflow of the 32-bit variable is possible inside a long cycle which utilizes a memsize-type loop counter. Constructors __________ to allow different approaches of object construction.

V3004. V3048. There is a probability of logical error presence. AUTOSAR. MISRA. > ? V3001. > . ? V5604. Verifying that a pointer value is not NULL is not required. :' operator, regardless of its conditional expression, always returns one and the same value. OWASP. Potentially unsafe double-checked locking. V3154. V1004. Subtraction, >, >=, <, <= should be applied only to pointers that address elements of the same array. > ? V734. V3039. Suspicious access to element by a constant index inside a loop. V729. V6077. The function expects the file to be opened in one mode, but it was opened in different mode. V6085. V3100. Initializer of a field marked by [ThreadStatic] attribute will be called once on the first accessing thread. String literal contains potential interpolated expression. Unexpected function overloading behavior. V5008. Property accessors use different backing fields. The 'switch' statement should have 'default' as the last label. Comparing objects of incompatible types. Consider inspecting the loop expression. An empty exception handler.

V550. V1050. Allocation of memory by the pattern "(X*)malloc(sizeof(Y))" where the sizes of X and Y types are not equal. Destructor of 'Foo' class is not declared as virtual.

Escuela Militar de Aviacin No.

Consider inspecting the loop expression. Possibly 'Total*' value was intended instead. MISRA.

Probably the '-=' should be used here. MISRA. The variable is assigned but is not used by the end of the function. Consider inspecting the expression. > ? Possible SQL injection. A suspicious label is present inside a switch(). Consider enabling the display of invisible characters in the code editor. InvalidClassException may occur during deserialization. Friend keyword can be used for a function in the private section of a class. The 'x' variable is assigned to itself. V799. The 'malloc' function is used to allocate memory for an array of objects that are classes containing constructors/destructors. V6031. Consider synchronizing the field on all usages. V515. The 'Foo' function is called twice in the specified expression to calculate length of the same string. OWASP. V2555. V614. MISRA. V2610. V5007.

V2553. > ? Suspicious use of BigDecimal class. The 'throw' operator does not have any arguments and is not located within the 'catch' block. Defining an absolute path to the file or directory is considered a poor style. OWASP. V3099. An excessive check can be simplified. V2519. V1048. The loop will not be executed. > ? V6013. Expression inside assert statement can change object's state. Please check projects and solution configurations. 'default': , , , . Consider inspecting the expression for function call. It is suspicious that the value 'X' of HRESULT type is compared with 'Y'. V711. V3005. Variables are initialized through the call to the same function. This pattern is suspicious. V670. OWASP. Return value of function is written to N-bit variable. V706. A 'wchar_t *' type string is incorrectly converted to 'BSTR' type string. V011. V521. V573. MISRA. Consider inspecting the statement of '*pointer++' pattern. Function should not contain labels not used by any 'goto' statements.

MISRA. Potential division by zero. V3152. V2508. Identifiers declared in the same scope and name space should be distinct.

Odd semicolon ';' after 'if/for/while' operator. Your comments will be displayed only after manual approval. Explicit type conversion from memsize to double type or vice versa. V6057. >2018 ? The 'operator &&', 'operator ||', 'operator ,' and the unary 'operator &' should not be overloaded. V621. A function with the same name as the class, but preceded with a tilde character (~) is called __________ of that class. The 'then' statement is equivalent to the 'else' statement. Suspicious declaration. V2530. V2617. , V1002. Call of the 'Foo' function will lead to buffer underflow. Compiler may delete 'memset' function call that is used to clear 'Foo' buffer. V6053. Octal constants should not be used. Comma may be missing. MISRA. Probably meant: *ptr != zero. Consider inspecting the expression. Argument of the '|' bitwise operation always contains non-zero value. V108. V531. > ? MISRA. . Pointer is compared with 'zero' value. Inline functions should be declared with the static storage class. Annotation that does not have 'RUNTIME' retention policy will not be accessible through Reflection API. V3123. V585. V5611. V109. Virtual table pointer will be damaged. The DllMain function throws an exception. AUTOSAR. AUTOSAR. Consider reviewing the source code that uses the container. V1081. V009. Variable is assigned but not used by the end of the function. V647. The macro with the 'setjmp' name and the function with the 'longjmp' name should not be used. Unsigned value is compared to the NN number. V3513.

V658. It will not compile because class body of Peacock is not defined. The '&=' operation always sets a value of 'Foo' variable to zero. Locking operations must be performed on the same thread. V735. Remember that 'a == b == c' is not equal to 'a == b && b == c'. operator are identical. V1013. It will not compile because a class cannot be protectedly inherited from other class. V3061. V6046. Wrong variable is probably used in the for operator as an index. Perhaps this is a mistake. V2554. V5002. V5616. Operands of the logical '&&' or the '||' operators, the '!' An 'else' branch may apply to the previous 'if' statement. V5605. Check the array initialization. > ? The resulting value could be inaccurate. > ? V810. Assigning potentially negative or large value as timeout of HTTP session can lead to excessive session expiration time. Decreased performance. The '? V659. Function receives an odd argument. V834. AUTOSAR. Consider inspecting the expression.

'else' keyword is probably missing. V523. V774. AUTOSAR. Incorrect index type: 'foo[not a memsize-type]'. V2586. V3096. V645. A part of conditional expression is always true/false if it is evaluated. V668. Team License Memory allocation and deallocation functions should not be used. Consider implementing event accessors explicitly or use 'sealed' keyword. V5304. The object could have been garbage collected before the 'Target' property was accessed. V832. V1071. > ? Original sorting order will be lost after repetitive call to 'OrderBy' method. , , , Dereferencing the result of null-conditional access operator can lead to NullReferenceException. V3094. The 'value' parameter is rewritten inside a property setter, and is not used after that. V3031.

V3011. V3111. V2597. It is highly probable that the semicolon ';' is missing after 'return' keyword. The variable is not used after copying. Use 'double.IsNaN()' method instead.

Moving an object in a return statement prevents copy elision. Consider inspecting type casting. There should be no user-defined variadic functions. IDisposable object is not disposed before method returns. Declaration should contain no more than two levels of pointer nesting. MISRA. The '<' operator should probably be replaced with '<<'. Consider creating a 'T' type object. MISRA. V819. By declaring it abstract using the virtual keyword. Checking value for null will always return false when generic type is instantiated with a value type. Unreachable code was detected. V3095. V3518. :' operator. Consider using the 'int' type. MISRA. V3012. V6010. Presence of #line directives may cause some diagnostic messages to have incorrect file name and line number. WPF: the names of the property registered for DependencyProperty, and of the property used to access it, do not correspond with each other.