🚀 go-pugleaf

One thing I hate about debugging are those dreaded infinite loops. I end up
losing more and more memory every time I have to end-task.
You'd think 768 megs of ram would be enough, but its like every time I do
that I can have less and less windows open without getting errors.

I was thinking, though. In each loop you could call
Application->ProcessMessages();
Run a GetAsyncKeyState timer (they usually take less than 1% cpu usage on
233 MHZ machines).
Add one line of code to each loop.
if(Canceled()) break;

Canceled would run Application->ProcessMessages(); and return the value of
Cancel.

Cancel would be a 'master cancel' value that the GetAsyncKeyTimer would set
if your form was focussed and a certain hotkey pressed.

This would cancel any and all loops, and then the application could exit
smoothly, or at least, more smoothly than before, and probably very smoothly
if you add try catch statements to your OnDestroy(etc) code in case you get
access violations, that way your program can still free most of its
memory...

Sound good?