18-03-2022, 05:01 AM
What I have found is that the final/virtual/override creates a chicken and egg scenario with regard to virtuals. Declaring a method final in a class that is final is itself redundant.
My scanner gives the following cyclical violation warnings
virtual method should be override or final...which leads to marking the method as override and re-running the scanner, which then says method should be final, so put both override and final on the declaration and it then complains that final must appear by itself. Trying final by itself complains that method should be override and we are back to the first case and it becomes acyclical problem.
Finally ended up disabling rules A10_3_[1..2]
My scanner gives the following cyclical violation warnings
virtual method should be override or final...which leads to marking the method as override and re-running the scanner, which then says method should be final, so put both override and final on the declaration and it then complains that final must appear by itself. Trying final by itself complains that method should be override and we are back to the first case and it becomes acyclical problem.
Finally ended up disabling rules A10_3_[1..2]