Are you sure there is a memory leak with that code snippet?

Yes, it is a bug confirmed by MSFT: http://support.microsoft.com/kb/817518 ------------------------- Don't worry, be happy :o)

Please be patient, and don't repost after just two hours. You will probably get an answer, but the answer might come from someone who is still asleep. Reposting the same question isn't a good idea. Alcohol. The cause of, and the solution to, all of life's problems - Homer Simpson

voorugonda prashanth wrote: when i call loadXML there is some memory leak How you are verifying this ? Can you show code ? voorugonda prashanth wrote: please give me a solution to avoid memory leak. Release memory allocated. As already suggested use smart pointers. Delete memory allocated using new. Prasad Notifier using ATL | Operator new[],delete[][^]

John Simmons / outlaw programmer wrote: Of course, I'd also like to add that he should consider other employment opportunities after that kind of question... :laugh::laugh: "It's supposed to be hard, otherwise anybody could do it!" - selfquote

I thought I was the only one that never had any bugs in my code :-D

WalderMort wrote: but there are instances where using malloc has proved to be better Sorry, WalderMort, I don't know what you're referring to by this statement. If you follow the link I provided in my previous post and scroll up a few lines, you will find this: Stroustrup wrote: There is no performance difference between malloc() and new when you take initialization into account. In my humble opinion, if you find yourself in a situation where you think you benefit from the use of ::malloc() in C++, you're probably not using the language in the way Stroustrup intended. This is also how I interpret his statement a little bit further down: Stroustrup wrote: If you feel the need for realloc() - and many do - then consider using a standard library vector. WalderMort wrote: needing to allocatate an instance without calling the c'tor I cannot possibly think that I will find myself in a situation where I actually want to use uninitalized data, the compiler would also complain about it. If you want to create a copy of an existing object, you don't use ::memcpy():omg: but you would rather use the copy constructor or the assignment operator. But that may be just me...:-> ...but I think not... "It's supposed to be hard, otherwise anybody could do it!" - selfquote

I'm not sure, but it would be VB way. You need to add reference to that component in your project and use it in like VB. Prasad Notifier using ATL | Operator new[],delete[][^]

Have you tried creating a typelib of the COM object or adding it to the references?

Try a "Rebuild all". It might help. Alcohol. The cause of, and the solution to, all of life's problems - Homer Simpson

Me too from hyderabad,India.:) Best Regards, Suneetha

BTW, 2GB is for 32-bit Windows, which is the total limit of stack plus heap plus none-user memory. Best, Jun

Now again i use from MSDN From the MSDN The CPaintDC class is a device-context class derived from CDC_** **_ whitesky

the object class must overload the comparison operators ( <, >, <=, >= ) and then, simply call std::sort(vec.beging(), vec.end()); TOXCCT >>> GEII power [VisualCalc 3.0  updated ][Flags Beginner's Guide  new! ]

Maxwell Chen wrote: It's a deep copy! :-D :) "Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow cheers, Alok Gupta VC Forum Q&A :- I/ IV

Sarath C wrote: See the below articles First Link of yours match with third link of mine :) "Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow cheers, Alok Gupta VC Forum Q&A :- I/ IV

Suppose one has a working application with the following structure COrgMainFrame and COrgView loaded via a dll or unrelated part of the application. At some point in time you need to change the behaviour of one of the classes, but you are prohibitted to do this at design time time. So you can't/may not create/use CMyNewView or CMyDifferentMainFrame. The only way is to implement this is at runtime. This means override the normal behaviour of the class at runtime, by loading a new windowproc function into the message handeling part of that window you want to change. Once this is done all windows messages passes your function first instead of the PreTranslateMessage function that normaly parses the messages. So one can delete certain messages being send to the normal PreTranslateMessage function or add new functions; and altering as such the behaviour of the Original class. This doesn't have anything to do with inheritance or objects this is 'normal' windows behaviour. Each windowclass needs to be registerd in windows, this is normaly done by the MFC classes at creation of the window, this is needed to let windows now what windowproc needs to be called for this kind of window. Using the technique explained above one can alter the behaviour of one single instance of that class/window without changing the behaviour of other instances of the same object. I hope I have explained it clearly ennough what I meant. :) Like i said before I always thought that this was called subclassing in windows codito ergo sum

voorugonda prashanth wrote: then why we need handle in MSG structure??? I assume you're referring to the hwnd HWND in the struct. We need this because, regardless of any threading issues, we still need to know which window the message is for. From MSDN on GetMessage  "The GetMessage function retrieves a message from the calling thread's message queue." Steve