On Apr 17, 2006, at 10:40 AM, Tom Tromey wrote:
"Casey" == Casey Marshall <[EMAIL PROTECTED]> writes:Casey> If nothing else, so I can verify that it is portable enough that I'mCasey> not breaking lots of peoples' builds just by including it. The standard approach would be to do feature checks in configure (e.g., for AF_UNIX, etc), and then have the code in local.c simply error out if the functionality is not available.
This is actually what the code does (depending on the ENABLE_LOCAL_SOCKETS macro being defined), the configure code just needs to do the right tests and defines.
Also, what autoconf macro tests if a C preprocessor macro (eg AF_UNIX or AF_LOCAL) is defined?
Then we wouldn't need an enable flag at all. Well, unless we thought this was a feature that would sometimes deserve disabling... but personally I doubt that it is.
Well, this is a GNU extension, so I thought it could use an --enable flag. But, since it seems that most on this list would prefer it to be enabled if supported by the OS, I'll change it to do that.
Thanks.
PGP.sig
Description: This is a digitally signed message part
