🚀 go-pugleaf

> > 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.

Not trying to be picky, but if #include <vcl.h> is always the first include
in any form, and if vcl.h calls upon winsock.h (indirectly) then wouldn't
that mean that winsock.h will always be included in the precompiler first?
and therefore requires #include <winsock2.h> prior to #include <vcl.h>.

I think I'm trying to confirm whether my first assumption is correct that
vcl.h is in fact calling upon winsock.h?

If vcl.h is not calling up winsock.h then I can look to find which of my
other headers is calling winsock.h and hopefully resolve this...I just don't
like having to include a mandatory #include <winsock2.h> on all forms even
though I'm not using any internet components.