🚀 go-pugleaf

Actually, you're right; I have Indy components installed and I will use them instead  - it's just for this one application anyway.

thanks...



Remy Lebeau (TeamB) wrote:
> "Mike K" <nospam@nospam.net> wrote in message 
> news:47eacf28$1@newsgroups.borland.com...
> 
>> I also need to open a standard TServerSocket to open a pipe
>> to another application. As soon as I drop this component onto
>> the form, the compiler complains about a multiple declaration
>> for 'fd_set', which is defined in both winsock.h and winsock2.h.
> 
> winsock.h and winsock2.h do not coexist together.  That is Microsoft's 
> mistake.  They copied all of winsock.h's data structures and macros into 
> winsock2.h, instead of having winsock2.h simply #include winsock.h for them 
> instead.  I do not know why they did that, but it is a real pain to get 
> around, and doubly so since you are involving the VCL.
> 
> Basically, you need to separate your winsock2.h-based code from your 
> winsock.h-based code.  Put them into completely separate units so the two 
> headers have no chance of colliding with each other.  Better if you can move 
> one of them into a completely separate project, such as a static .lib that 
> you can then include into the main application once compiled.
> 
>> Can I modify WinSock.hpp to call winsock2.h instead of winsock.h
> 
> I would not recommend that.
> 
>> For various reasons, I'd like to have (int the same application) the use
>> of both my standard Borland socket components and the WinPcap
>> library as well.
> 
> Do you have the option of using different TCP components?  Indy, for 
> instance, uses winsock2.h instead of winsock.h.  You may want to consider a 
> change anyway, since TServerSocket and TClientSocket are deprecated now.
> 
> 
> Gambit 
> 
>