🚀 go-pugleaf

> How about setting the condition so that it is always false
> and see if you still have a leak?  Seems like if the term
> that should be evaluated if the condition is true, got
> evaluated every time through the loop, then you would
> have an allocation that's discarded(leak.)  I dunno' why
> this would happen though.

Ok, I did some more testing.  Here is a simple way to reproduce the problem.
Create a project with a single form, drop a TTimer on it, set the interval
to 100 and add this code to the OnTimer event:

for(int i=0; i<100; i++)
{
    AnsiString cTest = (true) ? AnsiString("Pass").Trim() :
AnsiString("Fail").Trim();
}

Run it and watch your memory bleed away.  Here are all the possible
permutations:

AnsiString cTest = (true) ? AnsiString("Pass").Trim() :
AnsiString("Fail").Trim(); = LEAK
AnsiString cTest = (false) ? AnsiString("Pass").Trim() :
AnsiString("Fail").Trim(); = LEAK

AnsiString cTest = (true) ? AnsiString("Pass") : AnsiString("Fail"); = NO
LEAK
AnsiString cTest = (false) ? AnsiString("Pass") : AnsiString("Fail"); = NO
LEAK

AnsiString cTest = (true) ? AnsiString("Pass").Trim() : AnsiString("Fail");
= NO LEAK
AnsiString cTest = (false) ? AnsiString("Pass").Trim() : AnsiString("Fail");
= LEAK

AnsiString cTest = (true) ? AnsiString("Pass") : AnsiString("Fail").Trim();
= NO LEAK
AnsiString cTest = (false) ? AnsiString("Pass") : AnsiString("Fail").Trim();
= LEAK

So it seems that whenever the evaluated expression does a Trim(), memory is
leaked.  Why would this be?  Someone tell me I'm crazy and they can also
reproduce this so I can post it to QualityCentral.

Mark