Some other reasons:
- Some systems (read: Linux) do not have pthreads
- What if I said I'm running GCC on Microsoft Xenix? Is that POSIX-
compliant?
- Curses is not POSIX. It's Single Unix Spec, though.
- C99 is still new and although it's in POSIX, not many systems have
it (Plan 9 doesn't have complete C99)
On Feb 4, 2008, at 9:23 PM, David Arnold wrote:
On 03/02/2008, at 8:29 PM, Lyndon Nerenberg wrote:
Autoconf is nothing but a stinking rotten corpse that lives only
because the cult of GNU adherents cannot (no, refuse to) grok the
concept of POSIX.
the problem with POSIX is that it doesn't specify enough.
for instance, if you have to write some code to list the network
interfaces on a (*nix) machine, you have some that provide a
specific function to do so (getifaddrs), some where you should use
SIOCGIFCONF, another where SIOCGLIFCONF is better and one where
your best bet is to hope the /proc filesystem is mounted and read
from that.
POSIX doesn't help for things like this. and autoconf, for all its
failings, does.
d
