This is the mail archive of the cygwin-patches@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: recv/send revert patch


"Christopher Faylor" <cgf@redhat.com> wrote:
> Would it make sense to use recvfrom/sendto on systems that
support
> it by implementing a new wincap capability?

The main reason I chopped out the recv/send methods and used the
existing recvfrom/sendto methods instead was simply to eliminate
some code, i.e. if recvfrom with a couple of NULL arguments is a
drop-in replacement for recv then why have methods for both?
Other than that, there isn't any reason to use recvfrom rather
than recv AFAIK.

(What's particularly annoying is that it is only for one
particular situation where the replacement fails on NT4.0; but to
work around that would require having the code in the DLL anyhow,
so the saving is immediately lost.)

On that basis, I'd have thought it's just cleaner and easier to
drop what my initial patch was attempting and call the matching
winsock interface each time.

HTH,

// Conrad




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]