Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!gatech!cwjcc!tut.cis.ohio-state.edu!mailrus!uwmcsd1!marque!uunet!mcvax!unido!quando!harriman
From: harriman@quando.UUCP (Jay Harriman)
Newsgroups: comp.unix.questions
Subject: Re: X/Open compliance testing.
Keywords: X/Open portability lint C testing standards
Message-ID: <592@quando.UUCP>
Date: 6 Sep 88 11:40:04 GMT
References: <339@Grumpy.UUCP>
Reply-To: harriman@quando.UUCP (Jay Harriman)
Organization: Quantum GmbH, Dortmund, W-Germany
Lines: 33

In article <339@Grumpy.UUCP> wgh@Grumpy.UUCP (William G. Hutchison) writes:
>Is there a program or package that can check a group of C programs
>to verify that they conform to the X/Open portability standards?
>Something like lint or PFORT would do the trick, if it existed.
>


I am working for Quantum GmbH, in Dortmund, West Germany. We are a 
contractor to X/Open, doing quality assurance work.

As far as I know, there is no test package available for testing
pieces of software for compatibility to the X/Open Portability Guide.

There is, however, an X/Open System Verification Suite designed to 
test actual computer systems for compliance. I believe that it will 
be publically available in the near future.

For software to comply to the standard, you would have to make sure
that the commands, subroutines, header values, etc, etc, used in the 
product were only those described in the XPG. Even more important
and more difficult is to make sure that these elements have been 
applied with *only* the functionality as specified in the XPG.

To this end, perhaps you could have your system tested for compliance.
Afterwards you would know exactly what to use when developing and 
what not to.

For a person at Unisys to contact: C. Earl Porter, Unisys Corp.,
322 North Sperry Way, MS B2G11, Salt Lake City, UT  84116,
(!ihnp4!sp7040!cep).

Jay Harriman
harriman@quando.uucp