C / C++ / MFC

ON_COMMAND(ID_FILE_NEW,CWinApp::OnFileNew);

vikrams wrote:

while on gcc 2.95.3 on unix
I get an output like
1 4 8 0

Cedric Moonen wrote:

That's wrong. The code should throw an exception because you try to access the contents of an iterator outside the bounds of your vector.

vikrams wrote:

while on gcc 2.95.3 on unix
I get an output like
1 4 8 0

vector<int> myIntVector;

    // Add some elements to myIntVector
myIntVector.push_back(1);
myIntVector.push_back(4);
myIntVector.push_back(8);

vector<int>::iterator iStart = myIntVector.begin();
vector<int>::iterator iEnd = myIntVector.end();

while(iStart != iEnd)
{
    cout << *myIntVectorIterator << " "; //Should output 1 4 8
    ++iStart;
}</int></int></int>

George_George wrote:

Does it mean COM client (thread) and COM server no need to be the same type of thread model (e.g. STA, MTA, etc.)?

George_George wrote:

Here is the comments from the book ATL Internals about in-process server considerations,

--------------------
Any thread that calls CoGetClassObject or CoCreateInstance must already have joined an apartment, or the call will fail immediately. So, does that mean all objects exposed from in-process servers must be equally at home in single-threaded and multithreaded apartments so that random clients isn't cause harm? Fortunately, no.
--------------------