C / C++ / MFC

UINT threadproc(LPVOID lparam)//the thread callback funtion
{
	::MessageBox(NULL,"call the function succeefully","info",MB_OK);
	return 0;
}
extern "C" void __declspec(dllexport) dllext()//the dll export function
{
::MessageBox(NULL,"call the function succeefully in dllext()","info",MB_OK);
CWinThread*pThread=AfxBeginThread(threadproc,NULL,THREAD_PRIORITY_NORMAL,0,CREATE_SUSPENDED ,NULL);
pThread->ResumeThread();
}

void CMainFrame::OnBeginthread() 
{
	//when I click the menu context..the application frame will call this function
	typedef void (*Pdllfun)();
	HINSTANCE hdll=LoadLibrary("thread.dll");
	if(hdll==NULL)
		::MessageBox(NULL,"can not laod the dll","",MB_OK);
	Pdllfun pdllfun=NULL;
	pdllfun=(Pdllfun)::GetProcAddress(hdll,"dllext");
	if(pdllfun==NULL)
		::MessageBox(NULL,"can not laod the dll funion","",MB_OK);
	pdllfun();//call the dll function
	FreeLibrary(hdll);
	
}

0x00fd102d instruction references "0x00fd102d" memory can not be written

void CMainFrame::OnBeginthread() 
{
	// TODO: Add your command handler code here
	//when I click the menu context..the application frame will call the function
	typedef void (*Pdllfun)();
	HINSTANCE hdll=LoadLibrary("thread.dll");
	if(hdll==NULL)
		::MessageBox(NULL,"can not laod the dll","",MB_OK);
	Pdllfun pdllfun=NULL;
	pdllfun=(Pdllfun)::GetProcAddress(hdll,"dllext");
		if(pdllfun==NULL)
		::MessageBox(NULL,"can not laod the dll funion","",MB_OK);
		pdllfun();

::MessageBox(NULL,"hold the dll","",MB_OK);//when I add a MessageBox here to let the dll remains in the 
                                            //memory,the problem will not exist any more.  

FreeLibrary(hdll);
	
}

Iain Clarke wrote:

Imagine Wile E Coyote running off a cliff, running into mid air for a few seconds, looking down... that's what you've done to your code.

Mark Salsbery
Microsoft MVP - Visual C++

Iain Clarke wrote:

I wouldn't go any near MFC for the DLL at all, just plain vanilla Win32.

Mark Salsbery
Microsoft MVP - Visual C++

Saurabh.Garg wrote:

But I declare a single variable in a line. This way I can add a comment for each variable I use.

Saurabh.Garg wrote:

The problem is you can almost never predict how the class is going to be used at a later time.

Saurabh.Garg wrote:

I am not sure, but in certain cases adding const might help compiler to produce more optimized code.

Christian Flutcher wrote:

1 - Which is the preferred way of using the pointer symbol ?

Christian Flutcher wrote:

2 - Is it a good practice to append const with member function that doesn't modify any member variables?

Christian Flutcher wrote:

I understand why const member functions exists. But if we are not planning to make the class object as constant,

<font color="blue">class</font> foo { ... };
 
<font color="blue">const</font> foo f(<font color="green">/* some initialization parameters */</font>);

toxcct wrote:

you have an interview, don't you ?

int *pInt;

double dMoney = 0123456789.0123456789;
char szOldCppMoney[MAX_PATH] = {0};
char szNewCppMoney[MAX_PATH] = {0};
sprintf(szOldCppMoney,"%2.2f",dMoney);
LCID lc = MAKELCID(MAKELANGID(LANG_ENGLISH, SUBLANG_ENGLISH_US), SORT_DEFAULT);
GetNumberFormat(lc,0,szOldCppMoney,NULL,szNewCppMoney,ARRAYSIZE(szNewCppMoney));