Returned mail: Cannot send message for 3 days

[MAILER-DAEMON@ucbvax.Berkeley.EDU (Mail Delivery Subsystem)]

   ----- Transcript of session follows -----
421 wsmr-simtel20.army.mil.tcp... Deferred: Connection refused by wsmr-simtel20
.army.mil

   ----- Unsent message follows -----
Received: by ucbvax.Berkeley.EDU (5.63/1.43)
	id AA16757; Thu, 1 Apr 93 19:38:04 -0800
Received: from USENET by ucbvax.Berkeley.EDU with netnews
	for info-ada-ddn@wsmr-simtel20.army.mil (info-ada@wsmr-simtel20.army.mi
l)
	(contact usenet@ucbvax.Berkeley.EDU if you have questions)
Date: 30 Mar 93 21:28:21 GMT
From: emery@mitre-bedford.arpa  (David Emery)
Organization: The Mitre Corp., Bedford, MA.
Subject: Re: Ada cost breakpoints
Message-Id: <EMERY.93Mar30162821@goldfinger.mitre.org>
References: <9303291535.AA16997@eight-ball.boeing.com>
Sender: info-ada-request@wsmr-simtel20.army.mil
To: info-ada@wsmr-simtel20.army.mil

Open, Read, Write, pipes, Fork and Exec are included in POSIX
standards.  Sockets, for instance, are not currently in any approved
POSIX standards.  Therefore, code written using sockets is *NOT*
guaranteed portable in a POSIX environment (e.g.  Open VMS, CTOS or
POSIX-compliant MVS, for instance).  Sockets are a BSD extension
(which is now included in System V).  Sockets packages exist for other
operating systems, but they're not "open" in the sense of formally
standardized.  Your semantics may vary...

>It occurs to me that it might be sensible for programs to require
>that all OS interfaces which are not pre-defined in the language (e.g.,
>Text_IO, task stuff) be defined in Posix syntax.

Could you please explain this?  What is "Posix syntax"?  I'm not
familiar with that term...

			dave
			(IEEE P1003.5 POSIX/Ada Binding Technical Editor)