To help understand why libposix has different goals from other "libc"
implementations, consider the comparison below, listing some current posix
implementations (focus on GNU systems)


                       libposix   glibc   eglibc   uclibc   *BSD libc
1. cross platform          X        X       X       X
2. strict conformance      X
3. legacy code                      X       X       X          X
4. multi-standard support           X       X       X          X
5. extensions                       X       X       X          X
6. embedded targets                         X       X
7. ease of (cross)building X                X       X
8. support                 X                X       X          X

In 1 and 2 we see the main goals of libposix. We hope to have a working
POSIX 2008 system on every platform we support. In 3, 4, we see what
we don't want in libposix. The code should be as clean as possible, so
no legacy code is expected to appear, although that restriction is not really
strict. We don't expect to support older standards either, like POSIX 2001. In
5 we just repeat rule 2, with the remark that libposix should play well with
possible extensions (say, libgnu or libbsd). In 6 we notice that libposix
shouldn't target restricted environments, neither support "feature selection".
The platform either is able to support POSIX or it's not. In 7 we reaffirm
code cleaness, so that developers can easily build and rebuild libposix
painlessly. Finally, in 8, we claim that we expect to give friendly, fast and
efficient support for everyone that needs it.