C / C++ / MFC

Cedric Moonen wrote:

What's the point of your example ?? You throw something that is caught two lines under. Why do you need to throw an exception for such a thing ? That's just totally not adapted.

Cedric Moonen wrote:

But now, how can you inform the users of your object that something went wrong during construction of the object ? Well, in general you throw an exception out of your constructor.

George_George wrote:

In the exception handler of constructor.

// CDummyClass might throw an exception if it fails to construct<br />
void MyFunc<br />
{<br />
   try<br />
   {<br />
      CDummyClass test();<br />
      test.DoSomething();<br />
   }<br />
   catch (....)<br />
   {<br />
      // Ok CDummyClass failed to construct so we'll try something else.<br />
   }<br />
}

George_George wrote:

Agree?

George_George wrote:

Am I correct?

George_George wrote:

Do you have his email or MSN account?

George_George wrote:

I suggest to bring Bjarne to this forum to help to answer.

CreateCriticalSection<br />
EnterCriticalSection<br />
LeaveCriticalSection<br />
DestroyCriticalSection

EnterCriticalSection<br />
LeaveCriticalSection<br />

// Global variable
CRITICAL_SECTION CriticalSection; 

void main()
{
    ...

    // Initialize the critical section one time only.
    InitializeCriticalSection(&CriticalSection); 

    ...

    // Release resources used by the critical section object.
    DeleteCriticalSection(&CriticalSection)
}

DWORD WINAPI ThreadProc( LPVOID lpParameter )
{
    ...

    // Request ownership of the critical section.
    __try 
    {
        EnterCriticalSection(&CriticalSection); 

        // Access the shared resource.
    }
    __finally 
    {
        // Release ownership of the critical section.
        LeaveCriticalSection(&CriticalSection);
    }

    ...

}

Somnath_Mali wrote:

It always returns "Network connected State".