Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!swrinde!mips!decwrl!bacchus.pa.dec.com!decvax.dec.com!decvax!evans
From: evans@decvaxdec.com (Marc Evans)
Newsgroups: comp.unix.ultrix
Subject: Re: Ultrix 4.0: SVID/POSIX compliant?
Message-ID: <168@decvax.decvax.dec.com.UUCP>
Date: 30 Jul 90 11:13:57 GMT
References: <26B0A295.1137@tct.uucp>
Sender: news@decvax.dec.com.UUCP
Reply-To: evans@decvax.DEC.COM
Organization: Synergytics
Lines: 29

In article <26B0A295.1137@tct.uucp>, chip@tct.uucp (Chip Salzenberg) writes:
|> I'm looking for comments from people who have experience with C
|> development under Ultrix 4.0.  Specifically, I need to know whether
|> DEC has done a passable job at complying with ANS C, the SVID and the
|> POSIX.1 and .2 standards.

ANSI-C:	Both the MIPS compiler and the vax compilers have not been enhanced to
	the point that they could be called ANSI-C compliant. GNU-CC is still
	your best option for ANSI.

SVID:	Ultrix 4.0 is compatible with select pieces of SVID issue 2. I believe
	that the sales blurbs explain which of the select pieces DEC chose.

POSIX:	In 4.0, we have made extensive use of PCTS (Posix compliancy test suite)
	which tests the .1 capabilities. If you find items in 4.0 which are not
	.1 compliant, report a QAR, because this should not be the case. .2 on
	the other hand I don't believe has been fully addressed (yet).

XPG3:	As announced earlier this year, Ultrix 4.0 has been validated XPG3
	compliant (the base part). DEC did submit a few waivers, but these
	are being fixed rapidly and probably won't be noticed by the large
	majority of the users.

- Marc

===========================================================================
Marc Evans - WB1GRH - evans@decvax.DEC.COM  | Synergytics     (603)635-8876
      Unix and X Software Contractor        | 21 Hinds Ln, Pelham, NH 03076
===========================================================================