Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!snorkelwacker!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: <9002212102.AA00298@expire.lcs.mit.edu>
Date: 21 Feb 90 21:02:38 GMT
References: <49344@lll-winken.LLNL.GOV>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 20


    And in the end I will have done exactly that: simply rewritten
    XGetDefault using a different set of routines.

Perhaps not.  And even if you did, you'd at least have had to answer at
least one basic question (what to do for class names), and in the process
hopefully understood why XGetDefault as it stands is a crock.

    Again, I don't understand the reluctance to keep something usefully
    simple like XGetDefault around.

It is around.  It is simple.  You're trying to make it more complicated, by
arguing that a former abuse of it should still work. :-)

    Even the MIT software uses XGetDefault extensively.  In mit/clients I
    count 23 calls to XGetDefault in 4 clients (there are two more references
    to it in xrdb's manual page.)

Yes, 4 clients that we sorely wish we had had time to rewrite for R4, clients
largely left over from X10 days.