Path: utzoo!attcan!uunet!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!ncar!boulder!stan!ninja!toml
From: toml@ninja.Solbourne.COM (Tom LaStrange)
Newsgroups: comp.windows.x
Subject: Xrm differences
Message-ID: <1990Jun28.153531.3657@Solbourne.COM>
Date: 28 Jun 90 15:35:31 GMT
Sender: news@Solbourne.COM
Reply-To: toml@solbourne.com
Organization: Solbourne Computer, Inc.
Lines: 39


I have noticed a difference in behavior of the Resource Manager code
and after looking through some of the fixes that have been applied to
our Xlib lately, I can't seem to find the "fix" that caused the change.
Here's the details:

I have the following string on the right hand side of a resource
specification (never mind that it looks weird):

    "test"       \\ "\\" f.exec("test \#1234 &")


Using Xlib built with Xrm.c with the following header:

 * $XConsortium: Xrm.c,v 1.32 89/12/11 19:10:50 rws Exp $

The following string gets returned from the resource manager

    "test"       \ "\" f.exec("test #1234 &")


Using an Xlib built with this version Xrm.c

 * $XConsortium: Xrm.c,v 1.38 90/06/15 11:21:35 rws Exp $

The resource manager returns this string

    "test"       \\ "\\" f.exec("test \#1234 &")


The differences are obviously in the handling of the '\' character.
Can anyone shed some light on which should be the correct behavior?

Thanks,
Tom LaStrange

Solbourne Computer Inc.    ARPA: toml@Solbourne.COM
1900 Pike Rd.              UUCP: ...!{boulder,sun}!stan!toml
Longmont, CO  80501