On Tue, 12 Jan 1999, Daniel Koepke wrote:
>George wrote:
>>
>> It seems a newer version of Borland C++ includes winsock2.h
>> automatically which conflicts with the winsock.h included by
>> CircleMUD. Is there any #define we can use to detect Winsock2 and
>> avoid including the old Winsock code?
>
>Doesn't the winsock2.h file #define _WINSOCKAPI_, automatically
>preventing winsock.h from being included? If not, #define it, and
>that /should/ fix it. Of course, I could be wrong (what do I know
>about Windoze and Winsock?)...
I suppose I can look when I get back to the campus tomorrow, but that is
Microsoft Visual C++ 6.0 and not Borland C++. Microsoft doesn't seem to
have the problem currently, just Borland's. So basically I need someone to
look and perhaps make a list of changes/patch for me.
The current code will just do a #warning for Borland C++ til I hear
otherwise.
--
George Greer
greerga@circlemud.org
http://www.circlemud.org/~greerga/
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST