Bug#227386: libc6-dev: ENOTSUP==EOPNOTSUPP, which violates SUSv3
On Thu, Feb 23, 2006 at 04:14:40AM +0000, Brian M. Carlson wrote:
> Second, glibc claims (as I have just shown in another message) that it
> conforms to POSIX 1003.1-2001. Therefore, currently I can expect that
> the errors are different. Anyway, I don't want to have to work around
> every Unix's bugs. If I did that, then I'd have to provide my own copy
> of memcmp (yes, memcmp), because SunOS 4.1.3 (IIRC) compares the bytes
> as signed, not unsigned. Some versions of AIX have a broken strnlen,
> which would have to be fixed if I used it (I don't). Half of my code
> would be fixes for obviously non-standard-conformant behavior[0], and
> sometimes I'd have to break standards conformance even further[1]. Such
> fixes are not fun to write; I'd much rather be implementing new
> features.
You'd rather spend months arguing with distributors about trivial POSIX
compliance gotchas, which would be a substantial impact to fix in the
system libraries (whatever you may claim), and then depend upon brand
new fixed versions of the system libraries that probably only
Debian/unstable and no other distributor would ship?
A little pragmatism is always advised when dealing with portability.
Especially for a bug that will be allowed by a future version of POSIX.
--
Daniel Jacobowitz
CodeSourcery
Reply to: