To eliminate the V690 warning here, we need to remove the meaningless copy constructor.
The compiler will build the code, copying the class members in no way slower, if not even faster.
An amendment to this rule is that if Resource Acquisition Is Initialization (RAII) is used for the class members, the destructor may be left undefined (also known as The Law of The Big Two).
Because implicitly-generated constructors and assignment operators simply copy all class data members, one should define explicit copy constructors and copy assignment operators for classes that encapsulate complex data structures or have external references such as pointers, since only the pointer gets copied, not the object it points to.
The handling of this case is different for code compiled prior to C 11, and code compiled C 11 and after.
Both are derived from different versions of Scott Meyers Books [Next to the 2 different examples see the citations] For C 11 and after [Effective Modern C Item 17]: According to a Scott Meyers book, the following is valid code and will explicitly prevent any class that inherits from this interface from copying.As you can see, "The Law of The Big Two" is very important - that's why we have implemented the corresponding diagnostic in our code analyzer.Does the V690 diagnostic always reveal genuine errors? Sometimes we deal not with an error but just a redundant function.To fix the class, we need to implement a copy constructor: If the analyzer generates the V690 warning, please don't be lazy to implement an absent method.Do so even if the code works well currently and you are sure you remember the class' specifics.Here is an extract from Wikipedia: The rule of three (also known as the Law of The Big Three or The Big Three) is a rule of thumb in C that claims that if a class defines one of the following it should probably explicitly define all three: These three functions are special member functions.If one of these functions is used without first being declared by the programmer it will be implicitly implemented by the compiler with the default semantics of performing the said operation on all the members of the class.A copy constructor and a copy assignment operator shall be declared for classes that contain pointers to data items or nontrivial destructors.This Static Analysis rule requires that I have to adhere to the Rule of 3 (now rule of 5 if moves are included).So, I want to explicitly prevent the user from being able to copy any of these classes, but can not find a way to do so that eliminates the Static Analysis violation.Here is an example of what I have attempted: A.h Class A A:: A() A::~A() There are 2 cases that need to be covered by my code.