Search:
Type: Posts; User: Paul McKenzie
Search:
Search took 2.07 seconds.
-
November 26th, 2012, 10:59 AM
The only thing to go by is what you posted. From the code you posted, either CMemoryException is your own home-made class, or it's the MFC class. Since there was no header defining...
-
November 20th, 2012, 02:17 PM
You should have debugged into that call to new. What do you see when you debug inside of this call to "new"? Is there any place where the allocation failure is checked?
So the question is...
-
November 20th, 2012, 02:05 PM
The CMemoryException is an MFC class. Wherever you got this information from, it is pertaining strictly to MFC. There is no MFC in the original code you posted, except for CMemoryException, which...
-
November 19th, 2012, 04:50 PM
You're also mixing MFC exceptions with STL exceptions. That's what's confusing about your code. I don't see how your code could have compiled using the MFC classes, given that you didn't specify...
-
November 19th, 2012, 01:19 PM
Your code is using std::list, not std::vector.
Regards,
Paul McKenzie
-
November 19th, 2012, 12:36 PM
Placement-new explained.
http://www.parashift.com/c++-faq/placement-new.html
Regards,
Paul McKenzie
-
November 19th, 2012, 12:32 PM
If you are not calling "new" or "new[]" yourself, none of what you've stated is guaranteed to occur. There is no guarantee that copy construction is done under the hood, since copy construction can...
-
November 16th, 2012, 12:21 PM
Let's start at a common baseline, and that is your system and the code given to you at the link I gave you.
Please take the exact example posted at the link I gave you. Does it show the same...
-
November 15th, 2012, 09:05 PM
Nowhere in your sample are you calling operator new[] yourself.
The flaw in your entire example is assuming that list::push_back() does what you think it does in terms of the C++ routines to...
|
Click Here to Expand Forum to Full Width
|