The warning W511: Object 'xxx' created in try block is annoying because it is common practice to write code like this:

bla := nil;
blub := TBlub.Create
try
bla := TBla.Create;
// ...
finally
bla.Free;
blub.Free;
end;

I realize that is is difficult to determine whether the object variable is being initialized with nil (how far in front of the try do we look?) but we need a way to reduce the amount of such warnings otherwise they will just be turned off.

(I am sure I am not the first one to notice this, but I the look up did not find anything.)

FixInsightCL -- project=\source\example.dpr --rules=W507;508;C105;C106

Using an index specifier in format statements creates false positive W513 warnings.

ShowMessage(Format('%d %0:d', [1]));//OKAY - output "1 1"
ShowMessage(Format('%0:d %0:d', [1]));//OKAY - output "1 1"
ShowMessage(Format('%0:d %0:d %1:d', [1, 2]));//OKAY - output "1 1 2"
ShowMessage(Format('%0:d %0:d %1:d %d', [1, 2]));//ACTUALLY AN ERROR, because last %d requires a third arguments array item

Like this kind of
try
LMyObject := DoSomethingWhichSometimesRaiseExcptionWhichICantDoNothingOrByDesign;
except
{ Eat this exception because of this and that FixInSigntSuppressWarnings(W501) }
end;

Would be cleaner the use Comments IMHO than some compiler directive way present now (I think)

It would be helpful, if the C107 message "Class field name should start with 'F'" contained the class name and field name e.g. "Class field name 'TMyClass.SomeField' should start with 'F'"

We are using FixInsight in our build chain. Not calling inherited in destructor should be an exception. But not calling inherited in constructor should be a warning. To interprete so from build server it has to be two seperate rules.

The Delphi compiler warns you if a function may not have had its Result initialised, if it is a simple / unmanaged type (eg an integer.) However, it doesn't do this if it is a managed type, like an interface or string. IMO it should - not initialising a result is a problem - and it'd be great if this warning could be implemented in FixInsight.

This would be similar to the existing warning for destructors. If a constructor doesn't call an inherited constructor, it should warn.

awesome product!