Check if the paramter of a method have a prefix:

var Parameter: v

out Parameter: o

other Parameter: a

So you can see what type of parameter is used.

Methods like this with Unicodestring

procedure test(s: UnicodeString);

Should have

O801 CONST missing for unmodified string parameter 's'

I have downloaded Trial Version of fixinsight.But there are too many false positive warnings.
for example

 if not( IdTelnet1.Connected ) then
  begin
    Timer1Lan.Enabled := false;
    Timerc.Enabled := True;
    exit;
  end;
or

   b := sepdate(logstr, 22, 8, log.month, log.Day, log.Year);
          if b = false then
          begin
            ok := false;
            exit;
          end;
         ....

IF some //FI:CODE will become obsolete by the changes into the file, there shoudl be warnign that there is Ignore rule added, but it is not needed anymore.

Today I upgraded our test system to FI 2016.9. When I copied settings from DefaultSettings.ficfg into our config, I accidentally added two closing xml tags.

This invalid ficfg file caused a crash of FixInsight with an access violation in FixInsight.Services.dll. It was easy enough to solve, but a proper error message like "the configuration file '%s' is not a valid xml file" would be helpful.

There's a bug with the W504 detection in FixInsight 2016.04, when the class is declared in the implementation part of a unit.

In the following code, there should be a W504 and a W525 detected, but only the 504 is shown and it is shown in the wrong location.

unit W504Test;

interface

uses
  System.Classes;

// Declare class in implementation, only the 504 warning is thrown in destructor
// nothing is shown for constructor
implementation 

type
  TBinWriter = class
  end;

  TContentBuilder = class(TStringList)
  private
    FBinWriter: TBinWriter;
  public
    constructor Create(ABinWriter: TBinWriter);
    destructor Destroy; override;
  end;

// Declare class in interface, behaviour is correct
// implementation 

constructor TContentBuilder.Create(ABinWriter: TBinWriter);
begin
//  inherited Create;
  FBinWriter := ABinWriter;
end;

destructor TContentBuilder.Destroy;
begin
  FBinWriter := Nil;
//  inherited;
end;

end.

This FixInsight bug bit me really hard until I spotted the missing "inherited create" bug in my code...

With the current code, i got a fatal parser error:

unit Artikelmanager.OrmKonstanten;
interface
type
  TOrmFeldInfo = record
    Name: string;
    Laenge: Integer;
  end;
  KORMInfoDruckvorlage = class(TObject)
  public const
    Name: TOrmFeldInfo = (Name: string; Laenge: Integer);
  end;
  implementation
end.

Hello This is JH Jang from Korea.

Thank you for great tools.

Actually, I wasn't care it before using the FixInsight. I work with Windows 10 and Berlin 10.1.

If the property has a index(e.g. property foo[Index: Integer]: String read GetFoo, property bar[Idx: Integer]: Integer index 1 read GetBar ...), the get method's parameter cannot declared with const type in a every case.

I hope to filtering it.

Best regard.