Ambiguities in statistics screen and callertable

[Dany]

This has not popped up in v4.10, it is already long the case in older mP versions.
Furthermore it does not hamper software development with mP v4.10 (nor the compiler, nor the IDE are erroneous here).

Hi, there are some ambiguities and subsequent errors in the statistics screen and the callerfile if 2 routines have the same name in different units.

This is the code of a test project:

Code: Select all

program SameProcNames;
uses Unit1, Unit2;
begin
  { Main program }
  Unit1Procedure;
  Unit2Procedure;
end.

unit Unit1;
procedure Unit1Procedure;
implementation
procedure SameName(xxx: byte);
begin
end;

procedure Unit1Procedure;
begin
  SameName(20);
end;

end.

unit Unit2;
procedure Unit2Procedure;
implementation
procedure SameName(yyy: byte);
begin
end;

procedure Unit2Procedure;
begin
  SameName(50);
end;

end.

As you can see, both Unit1 and Unit2 contain a local procedure with the same name, which is indeed completely legal. The compiler handles this well, no problems there.

The problems occur in

- the caller table, it shows:

Code: Select all

main
     Unit1Procedure
          SameName
     Unit2Procedure
          SameName

It seems like procedure "SameName" is called twice, while in reality there are 2 different "SameName" procedures.

- the "Statistics Function tree", it shows:

As you can see, the statistics think that the 2nd "SameName" is also in Unit1.

- the "Statistics Function charts": the difference between the different "SameName"s can not be seen. This is only a very minor remark.

Thanks in advance!

[zristic]

Thanks for the report.