From xemacs-m  Sat Dec 14 00:33:12 1996
Received: from altair.xemacs.org (steve@xemacs.miranova.com [206.190.83.19]) by xemacs.cs.uiuc.edu (8.8.3/8.8.3) with ESMTP id AAA11151 for <xemacs-beta@xemacs.org>; Sat, 14 Dec 1996 00:33:10 -0600 (CST)
Received: (from steve@localhost)
          by altair.xemacs.org (8.8.4/8.8.4)
	  id WAA05378; Fri, 13 Dec 1996 22:43:14 -0800
Sender: steve@xemacs.org
To: xemacs-beta@xemacs.org
Subject: Re: Key names: XEmacs vs. RMS
References: <199610011517.KAA26110@nvwls.cc.purdue.edu> <199610042047.QAA18259@anthem.CNRI.Reston.Va.US>
X-Url: http://www.miranova.com/%7Esteve/
Mail-Copies-To: never
X-Face: #!T9!#9s-3o8)*uHlX{Ug[xW7E7Wr!*L46-OxqMu\xz23v|R9q}lH?cRS{rCNe^'[`^sr5"
 f8*@r4ipO6Jl!:Ccq<xoV[Qz2u8<8-+Vwf2gzJ44lf_/y9OaQ`@#Q65{U4/TC)i2`~/M&QI$X>p:9I
 OSS'2{-)-4wBnVeg0S\O4Al@)uC[pD|+
X-Attribution: sb
From: Steven L Baur <steve@miranova.com>
In-Reply-To: "Barry A. Warsaw"'s message of Fri, 4 Oct 1996 16:47:01 -0400
Mime-Version: 1.0 (generated by tm-edit 7.95)
Content-Type: text/plain; charset=US-ASCII
Date: 13 Dec 1996 22:43:14 -0800
Message-ID: <m2raktiq2l.fsf@altair.xemacs.org>
Lines: 38
X-Mailer: Red Gnus v0.72/XEmacs 20.0

>>>>> "BAW" == Barry A Warsaw <bwarsaw@cnri.reston.va.us> writes:
>>>>> "JJN" == Joseph J Nuspl <nuspl@nvwls.cc.purdue.edu> writes:

JJN> XEmacs uses an underscore in the names of extended keys while
JJN> the RMS version uses dashes (i.e. kp_add vs kp-add).

JJN> Is there a history behind this?  Is there any reason why they
JJN> should be named with an underscore instead of a dash?  If
JJN> not, I vote for changing them to dashes.

BAW> Do you intend to disallow underscored keysyms?  I'd say, allow them
BAW> for the 19.15 release, but issue warnings and give people one major
BAW> release cycle to change their code.

They've now been changed to dashes in 20.0-b32.  Now, how best to
handle the problems of backwards compatibility?

I liked Bill Dubuque's suggestion:

Bill> A general way to do this is to extend the byte-compiler to allow
Bill> global symbol-macros (which should be trivial to do). E.g.

Bill> (defsym kp_add 'kp-add)		; alias for backward compatibility 

Bill> Recall that symbol-macros allow you to associate a macro definition
Bill> with any symbol reference; the macroexpansion phase of the compiler
Bill> simply replaces such a symbol with the result of evaluating the 
Bill> macro definition of the symbol.  E.g. the above is analogous to

Does anyone wish to code this?

Otherwise, I'm looking at changing the lookup code to convert to
dashes if it's given a keysym with underscores.
-- 
steve@miranova.com baur
Unsolicited commercial e-mail will be billed at $250/message.
"That Bill Clinton.  He probably doesn't know how to log on to the
Internet."  -- Rush Limbaugh, noted Computer Expert

