Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!think!mintaka!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: Does anyone have a fix for R4/PL1 XGetDefault?
Message-ID: <9002191921.AA01528@expire.lcs.mit.edu>
Date: 19 Feb 90 19:21:21 GMT
References: <47970@lll-winken.LLNL.GOV>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 17


    Under R4, XGetDefault doesn't work 100%.

Yes, it does (modulo the bug in the prototype declaration).

    If you attempt to do an XGetDefault(dpy, prog, "foo.bar"), XGetDefault
    won't break the string "foo.bar" up into separate ``Quarks'' and therefore
    won't match the desired resource.

That's correct.  XGetDefault is *not supposed* to handle multi-level resources,
it was only designed to handle single-level resources.  I suspect it is largely
by accident that abuse of it worked in R3.

    I've got a bug report in to MIT, but I don't know when
    we'll see a fix from them.

I don't think you'll see one from us, since it isn't considered a bug.