🚀 go-pugleaf

"Daniel Stevenson" <daniel@ocreage.com.au> wrote in message
news:438bd29a@newsgroups.borland.com...

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

You can include winsock2.h before vcl.h manually.  And let's not forget that
vcl.h itself is not a real header file in the first place, but a placeholder
that the precompiler substitutes with another header based on the Project
features being used.

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

vcl.h itself is not, no.  What does, however, is windows.h and winsock.hpp.

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

Try using precompiled headers.  Then you wouldn't include either one in your
forms, but would include your own custom header instead.


Gambit