Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site plus5.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!mtuxo!drutx!ihnp4!plus5!hokey%plus5
From: hokey%plus5@plus5.UUCP
Newsgroups: mod.std.mumps
Subject: Implementation and Software Compliance
Message-ID: <890@plus5.UUCP>
Date: Fri, 20-Sep-85 20:20:03 EDT
Article-I.D.: plus5.890
Posted: Fri Sep 20 20:20:03 1985
Date-Received: Sat, 21-Sep-85 06:19:29 EDT
Sender: hokey@plus5.UUCP
Reply-To: hokey@plus5.uucp
Organization: Plus Five Computer Services, St. Louis
Lines: 29
Approved: hokey@plus5.uucp

Distribution:
Volume-Issue: 2.4

I believe the MDC should include in X11.1-198x a statement similar to the
one which the C Standards Committee (P1003) states in X3J11/85-008:

	A.7 Compliance

	  A *strictly conforming program* must use only those features of
	the language and library specified in this standard, must not produce
	output dependent on any implementation-defined characteristic, and
	must not exceed any minimum implementation limit.

	  A *conforming hosted implementation* must accept any strictly
	conforming program.  A *conforming freestanding implementation*
	must support all the features of the language specified in Section C,
	and provide the standard header <limits.h> specified in Section D
	(Library).  A conforming implementation may have extensions, which
	must not alter the behavior of a strictly conforming program (except
	perhaps by requiring the replacement of identifiers that conflict
	with new keywords or library symbols).

	  A *conforming program* is one that is acceptable to a conforming
	implementation.

	  An implementation must be accompanied by a document that defines
	all implementation-defined characteristics and all extensions.

	NOTE
	  Strictly conforming programs are intended to be maximally portable.
	Conforming programs may depend upon nonportable features of a
	conforming implementation.


Brought to you by Super Global Mega Corp .com