C / C++ / MFC

Error	1	error C2061: syntax error : identifier 'LPSECURITY_ATTRIBUTES'
Error	2	error C2061: syntax error : identifier 'LPSECURITY_ATTRIBUTES'
Error	9	error C2061: syntax error : identifier 'LPSECURITY_ATTRIBUTES'
Error	10	error C2061: syntax error : identifier 'LPSECURITY_ATTRIBUTES'
Error	12	error C2061: syntax error : identifier 'LPSECURITY_ATTRIBUTES'
Error	13	error C2061: syntax error : identifier 'LPSECURITY_ATTRIBUTES'
Error	14	error C2061: syntax error : identifier 'LPSECURITY_ATTRIBUTES'
Error	15	error C2061: syntax error : identifier 'LPSECURITY_ATTRIBUTES'
Error	21	error C2061: syntax error : identifier 'LPSECURITY_ATTRIBUTES'
Error	22	error C2061: syntax error : identifier 'LPSECURITY_ATTRIBUTES'
Error	23	error C2061: syntax error : identifier 'LPSECURITY_ATTRIBUTES'
Error	24	error C2061: syntax error : identifier 'LPSECURITY_ATTRIBUTES'
Error	26	error C2061: syntax error : identifier 'LPSECURITY_ATTRIBUTES'
Error	27	error C2061: syntax error : identifier 'LPSECURITY_ATTRIBUTES'

---

The only programmers that are better than C programmers are those who code in 1's and 0's.....

Programm3r
My Blog: ^_^

#include "stdafx.h" // NO '#include' here...
#include <conio.h>
#include <windows.h>
#include <winbase.h>
#include <winuser.h>

int _tmain(int argc, _TCHAR* argv[])
{
	printf("Just testing!!!\n");
	_getch();
	return 0;
}

---

The only programmers that are better than C programmers are those who code in 1's and 0's.....

Programm3r
My Blog: ^_^

toxcct wrote:

what compiler do you use exactly ?

---

The only programmers that are better than C programmers are those who code in 1's and 0's.....

Programm3r
My Blog: ^_^

Rene D wrote:

Are there any advantages with VS2005 compared to VS6?

for (int i = 0; i < 5; i++)
{
    // do something
}

for (i = 0; i < 5; i++)
{
    // do something
}

for (int i = 0; i < 5; i++)
{
    // do something
}

for (int i = 0; i < 5; i++)
{
    // do something
}

int i;
for (i = 0; i < 5; i++)
{
    // do something
}

for (i = 0; i < 5; i++)
{
    // do something
}

John Simmons / outlaw programmer wrote:

There are MANY changes to MFC. The most damaging involves COleDateTime. It seems MS decided that a m_dt value of 0.0 (12/31/1899) is now COleDateTime::invalid, despite the fact that COleDateTime supports dates all the way back to 12/31/100 (generates a negative value for m_dt). What a pain in the ass.

John Simmons / outlaw programmer wrote:

This is my hell.