irrnetlite probs - winsock dosent like me

[ortsa]

Elp, iv added irrnet and enet to my project and all is fine except for when i include irrnet.h or enet.h i get loads of errors from winsock, they are all similar heres a sample -

winsock2.h(212) : error C2011: 'hostent' : 'struct' type redefinition

There are ones about macro and function redefinition aswell.

How can i stop this from happening?

Im using visual studio 2005

[christianclavet]

I'm really not an expert (C++ and winsock), but this message seem to indicate that one of your include is redefining the same STRUCT structure block again. Check for a duplicate name somewhere in your code to see if that's true. (duplicate STRUCT block definition)

Perhaps you put the same include somewhere in your code...

[ortsa]

ok will do

[Acki]

maybe you don't use guard blocks in your header files ???

[ortsa]

well after some tweaking around the problem has just gone away and everythings working

Btw what do you mean by "guard blocks"

Weird

[randomMesh]

These things are called include guards.

[ortsa]

Oh right im just not familiar with that name i use pragma comment all the time

[randomMesh]

Oh right im just not familiar with that name i use pragma comment all the time

I meant Acki.

[Acki]

These things are called include guards.

[randomMesh]

Write them an email and ask to correct this. Thought the C::B guys knew better.

[rogerborg]

Elp, iv added irrnet and enet to my project and all is fine except for when i include irrnet.h or enet.h i get loads of errors from winsock, they are all similar heres a sample -

winsock2.h(212) : error C2011: 'hostent' : 'struct' type redefinition

This is actually a classic Microsoft snafu. If you compile windows.h - by which I mean include it directly or include anything that includes it - before winsock2.h, then it explodes spectacularly. You have to ensure that you include winsock2.h before anything that includes windows.h

Suck it and see.

Code: Select all

#include <windows.h>
#include <winsock2.h> // ASSPLOSION!

void main(void) { }

Code: Select all

#include <winsock2.h> // Works...
#include <windows.h> // ...fine

void main(void) { }

[randomMesh]

Code: Select all

void main(void) { }

OMG! main() returns an int.

[Dark_Kilauea]

Code: Select all

void main()

Is a perfectly valid definition of main. The majority of C/C++ compilers will accept it, making it a kind of de facto standard.

Code: Select all

 int|void main(int argc, char *argv[]) { } 

(or argv** if you really wanted to)

[randomMesh]

Code: Select all

void main()

Is a perfectly valid definition of main. The majority of C/C++ compilers will accept it, making it a kind of de facto standard.

No, no, no!. A C99 standard compliant compiler could show undefined behaviour. Never ever use void main()!

[hybrid]

I think it's even for C98 C++, but it's also just for the exit value. If you ignore the exit value it won't do any harm (though it's ugly to still use void there )