1 Jan
2022
1 Jan
'22
11:52 p.m.
https://bugs.winehq.org/show_bug.cgi?id=52250
--- Comment #9 from Zebediah Figura z.figura12@gmail.com --- Actually it occurs to me that the WS_ prefix is completely broken now, since ws2_32.dll itself doesn't use it. I.e. you can use WS_* definitions, but you can't link to WS_* functions.
It is a bit out of scope of this bug report (which isn't trying to use windows sockets at all), but I guess I can't figure out how to answer the original question without knowing what exactly we want to preserve in terms of backwards compatibility. E.g. should we preserve the ability to use the WS prefix? should we preserve the ability to link to either Win32 or Unix sockets simply depending on whether -lws2_32 is specified?
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.