> I think all of you who replied mised the point. We all know that lots of things
> can cause access violations. I get one regularly in D3 when I install new
> components. But there is a distinction between one in my code that I have
> written and one from some other part of the system. And it used to be that you
> could tell easily the difference, now you can't.
Except that object references are not initialised to nil for you... They usually will
be but it's not guarenteed... Global references and class fields are initialised
however. I guess it's that in the general case you cannot identify by the
Violation address whether the programmer error was lack of initialisation or
use after release.
--
Aaron Scott-Boddendijk
Jump Productions
(07) 838-3371 Voice
(07) 838-3372 Fax
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
