From: Nello Sestini [mailto:[EMAIL PROTECTED]]
> So really - this "replace" trick isn't as remarkable as it first
> sounded.
>
> "replaced" really just means "hides" - but the other function is still
> "there" and available via typecasting etc.
Correct
Despite the cuteness factor (8 out of 10 from the Russian judge :-), I'd
have to say that generally you want to avoid hiding static methods in this
way - it just causes confusion. The only reason I did it was, as I said to
Aaron, because I wanted to hide TObject.Create at compile time, which would
have been easy if I hadn't also needed to overload two descendant
parameterised Creates (the fact that TObject.Create is overloaded as well is
a quirk of overload, useful most of the time but not in my particular case).
I think hiding Create in that way is a neat, if odd, solution. But I've
only ever had cause to do it the once.
Cheers,
Carl
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
