[comp.windows.x] Bug With . In Executable Name??????

kit@EXPO.LCS.MIT.EDU (Chris D. Peterson) (05/30/90)

>	I have a problem where toolkit applications that have a period (.)
>	in the executable filename...

Don't do that.  The application name is used in the resource database, and the
only valid characters for a resource name are (a-z, A-Z, 0-9, _, -).  Any other
characters in an application name may confuse the resource manager, which loads
the command line arguements, and resources for all Xt applications.  The
characters ('*', '.', and ':') are particularly bad.

> I'm not sure if it is a bug or a configuration problem here.  

I wouldn't really call it either, it is just a limitation of the system.  There
is really no way to solve this problem, so the only thing I can suggest is
"Don't do that."

  
						Chris

ben@hpcvlx.cv.hp.com (Benjamin Ellsworth) (05/30/90)

Why can't the gods of Xt implement backslash processing for reading the
left-hand side of the resource specifier?  It's not hard, and it was
done for the right-hand side.  Then you could just put \. in the
application name.

A trivial bug and a trivial fix.  Is there a reason it won't appear in
the next release?

-----------------------------------------------------------------------
Benjamin Ellsworth      | ben@cv.hp.com                | INTERNET
Hewlett-Packard Company | {backbone}!hplabs!hp-pcd!ben | UUCP
1000 N.E. Circle        | (USA) (503) 750-4980         | FAX
Corvallis, OR 97330     | (USA) (503) 757-2000         | VOICE
-----------------------------------------------------------------------
                     All relevant disclaimers apply.
-----------------------------------------------------------------------