Re: Why no socket package in the standard ?

["Peter C. Chapin" <PChapin@vtc.vsc.edu>]

On Wed, 25 May 2011 06:01:06 +0200, Yannick Duchêne (Hibou57) wrote:

> Then I don't believe POSIX is a standard the same way Ada is a standard.
> Ada started as a standard from requirements, while POSIX started as a
> standard from existing features : its purpose was to be a standard for
> UNIX systems… so anyone can bet this is not surprising then if UNIces
> seems more POSIX compliant than others. Or may be UNIX is the only one
> legitimate OS base ? (I believe someones believe this, indeed). POSIX is
> not more a standard than PHP or Python are.

I think that's an inaccurate characterization of POSIX.

POSIX is, in fact, a standard. It was originally created by the IEEE. 
See, for example:

     http://pubs.opengroup.org/onlinepubs/009695399/

From the abstract:

"This standard defines a standard operating system interface and 
environment, including a command interpreter (or "shell"), and common 
utility programs to support applications portability at the source code 
level. This standard is the single common revision to IEEE Std 
1003.1-1996, IEEE Std 1003.2-1992, and the Base Specifications of The 
Open Group Single UNIX Specification, Version 2. This standard is 
intended to be used by both applications developers and system 
implementors. It comprises four major components (each in an associated 
volume)"

It is true that POSIX was designed to standardize the existing practice 
in the Unix community. This is typical of the way standards are usually 
created; it is the history of the Ada standard is unusual.

It also true that autoconf is a travesty... a throwback to a darker age 
when the POSIX standard did not exist (or at least was not widely 
implemented).

Peter