Path: utzoo!utgpu!watserv1!watmath!att!att!pacbell.com!ucsd!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!uflorida!gatech!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: Xlib code/doc discrepancies
Message-ID: <9010232241.AA03428@expire.lcs.mit.edu>
Date: 23 Oct 90 22:41:42 GMT
References: <751@igor.Rational.COM>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 14


    What is the "definition of the truth" for Xlib?

The specification, of course.

    An example is the definition of a resource name:
    the docs say (around page 224) that only alphanumerics, underscores,
    and dashes are allowed in component names, but XrmStringToQuarkList et
    al cheerfully accept all manner of "illegal" characters.

You should treat this as an example of an implicit statement:  "The
specification says the argument must satisfy <blah>, and if the argument
doesn't satisfy <blah>, the results are undefined."  Naturally, the
implementation has to choose some result.