Re: multiple symbols of select(), do they matter?
Re: multiple symbols of select(), do they matter?
- Subject: Re: multiple symbols of select(), do they matter?
- From: Terry Lambert <email@hidden>
- Date: Sun, 07 Sep 2008 09:43:19 -0700
On Sep 7, 2008, at 2:49 AM, Jean-Daniel Dupas <email@hidden>
wrote:
Le 7 sept. 08 à 10:59, Luke Daley a écrit :
On 07/09/2008, at 6:42 PM, Jean-Daniel Dupas wrote:
Why you do no simply call the matching function instead of using
the same select call for all variants ?
for example
int select_unix2003(int nfds, fd_set * __restrict readfds, fd_set
* __restrict writefds, fd_set * __restrict errorfds, struct
timeval * __restrict timeout) {
my_before_select();
int result;
int (*real_select)(int nfds, fd_set * __restrict readfds,
fd_set * __restrict writefds, fd_set * __restrict errorfds, struct
timeval * __restrict timeout) = dlsym(RTLD_NEXT, "select$UNIX2003");
result = real_select(nfds, readfds, writefds, errorfds, timeout);
my_after_select();
return result;
}
That's what I am looking to do, was more curious about what the
_actual_ differences are with the different symbols.
--
I don't know is there is a doc that explains all differences, but at
least, there is this:
$1050 => Mac OS X 10.5 and later behavior change
$DARWIN_EXTSN => Extended behavior beyond standards
$INODE64 => 64-bit ino_t values
$LDBL128 => 128-bit long double support (32-bit PowerPC only)
$UNIX2003 => UNIX™ conformance
$NOCANCEL => (used internally)
Generaly, the NOCANCEL variant is a variant that does not have posix
thread cancelation point (but should according to the standard).
This was done to avoid binary incompatibility with people who used the
test check. It was probably overcautios, but it was for you.
-- Terry _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden