About the author
I was writing a game component in Delphi, and somehow, whenever the game's component settings got changed, the game was leaking memory.
Using MemCheck with Delphi 7 SP 1, I managed to figure out where the memory leak was, and fixed the leak.
MemCheck is a free tool, which comes with complete source code. In the initialization section of any unit, preferably, the first unit that is listed in the project's clause, issue a call to MemChk.
When you close your application, MemCheck opens up your editor, and displays all the stack calls. Each stack trace is shown with the number of bytes leaked, and the number of times called.
If you're a programmer worth your weight in either dilithium or trilithium, you should be able to work out where your memory leaks are from there.
Continued discussion of undocumented Delphi 8 Property Access Specifiers, and other ways of adding and removing delegates / events handlers, including clearing the list of all the delegates / event handlers.
This article discusses the new Delphi 8 property access specifiers.
A method pointer is now the same as a global procedure, ie, procedure of object = procedure.