SiComponents Forums

Also, the code that is produced for MessageBox(0, siLang1->GetTextOrDefault("IDS_xx").c_str(), siLang1->GetTextOrDefault("IDS_yy").c_str(), MB_OK); seems fine: first twice { construction of parameter-AnsiString and result-AnsiString, call to GetTextOrDefault }, then the MessageBo...

... that has to do with buggy handling of temporary objects used during the construction of arrays.

Just found this totally by chance:

http://qc.borland.com/wc/qcmain.aspx?d=668

So it seems we have a neatly isolated problem here.

Yes, in general using GetTextOrDefault only in very simple constructs seems to be a good idea. Or updating to Turbo C++...

So is delete[] ok for the returned char *?

I think I have found the source of the AV. The GetTextOrDefault functions take "const AnsiString" as an argument, meaning in C++Builder a temporary AnsiString is constructed out of whatever parameter is passed. However, previous versions of Builder are buggy when handling temporaries. This...

Using plain delete[]?

Hi there,

just a short question: how/when is freeing the memory which seems to be allocated by GetTextOrDefaultC done, or do I do it myself? Trying to track down an AV here...

Greetings,
khs