I have experienced this bug many times before but it has gone away when
the code is recompiled. The IDE warns me that some property in my code
is not in the form. But it's not a property at all, it's a function or
procedure in this case. It's making me insane. Argh!
W
TMyDataModule = class(TDataModule)
//... snippage ...
private
function GetMethod(index:Integer):TTekMethod; // THIS CLASS NOT
DEFINED IN THIS UNIT. MOVE ME, AND NO PROBLEMS
function GetTekMdsUserIniFilename:String; // FIRST WITH THIS SIGNATURE!
function GetTekMdsIniFilename:String; // SECOND WITH SAME
SIGNATURE! DIES HERE!
function GetDisabledMethods:TStrings;
function GetDefaultMethodName:String;
// .. snip
end;
The two-way tools parser dies, with this "does not have corresponding
component" error.
1. This failure pattern does not reproduce when I try it in a standalone
project.
2. If you move the first declaration (function
foo(bar:bat):TSomeClassDefinedSomewhereOtherThanThisUnit) so it's not
the first declaration the problem goes away.
W
> function GetTekMdsUserIniFilename:String; // FIRST WITH THIS
> SIGNATURE! function GetTekMdsIniFilename:String; // SECOND WITH
> SAME SIGNATURE! DIES HERE!
Sounds a lot like a "don't do that" bug <g>
--
Dave Nottage [TeamB]