🚀 go-pugleaf

"Daniel Stevenson" <daniel@ocreage.com.au> wrote in message
news:43824b20$1@newsgroups.borland.com...

> I therefore had to include "#include <winsock2.h>" before my
> "#include <vcl.h>" which now leaves me with quite a number of
> warnings about "[C++ warning] _prolog.h(41): W8059 Structure
> packaging size has changed size"

That has nothing to do with winsock.h or winsock2.h.  That warning is a side
effect of Borland changing to a different STL library in BCB 6.  The warning
is safe to ignore.

> According to my research, the windows.h calls upon windows.h
> which in turn calls upon winsock.h and therefore the only way to
> stop the errors that are generated is by including winsock2.h prior
> to vcl.h.  But if I can compile a form that is directly using the indy
> components without first including winsock2.h, how does this not
> cause a problem with winsock.h?

If winsock2.h gets included into the precompiler before winsock.h, then
winsock2.h disables winsock.h automatically.


Gambit