X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1463" "Mon" "22" "June" "1998" "14:14:03" "+0200" "Hans Aberg" "haberg@MATEMATIK.SU.SE" nil "33" "Re: l3 function names" "^Date:" nil nil "6" nil nil nil nil nil] nil) Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1]) by mail.Uni-Mainz.DE (8.8.8/8.8.8) with ESMTP id OAA07372; Mon, 22 Jun 1998 14:14:15 +0200 (MET DST) Received: from lsv1.listserv.gmd.de (192.88.97.2) by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <7.7E9E651A@listserv.gmd.de>; Mon, 22 Jun 1998 14:14:12 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 367497 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 22 Jun 1998 14:14:06 +0200 Received: from mail.nada.kth.se (root@mail.nada.kth.se [130.237.222.92]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id OAA12549 for ; Mon, 22 Jun 1998 14:14:04 +0200 (MET DST) Received: from [130.237.37.30] (sl80.modempool.kth.se [130.237.37.106]) by mail.nada.kth.se (8.8.7/8.8.7) with ESMTP id OAA13984 for ; Mon, 22 Jun 1998 14:13:55 +0200 (MET DST) X-Sender: su95-hab@mail.nada.kth.se Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <199806211738.TAA04827@relay.urz.uni-heidelberg.de> Date: Mon, 22 Jun 1998 14:14:03 +0200 From: Hans Aberg Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: l3 function names Status: R X-Status: X-Keywords: X-UID: 2583 At 19:36 +0100 98/06/21, Javier Bezos wrote: >Undescore in names >~~~~~~~~~~~~~~~~~~~ >Changing the _ catcode prevents from using explicit subscript characters. >I think there are better candidates: "other" character except =, <, >, >. (sadly), , (ie, comma), - and +. (Namely /, !, ?, : (already used), ;, >@, |...) This is something I worried about at first. But it is possible to build a new development level above the fundamental one where _ works as usual: Then one would either not be able to use command names with _, or use a special command to invoke them or create them. For example, within <...>, _ works as an underscore space, and without as a subscript command. So I think one should not worry about it at this the most fundamental development level, and just use whatever is best for describing the logical structure. >Argument specifiers >~~~~~~~~~~~~~~~~~~~~ .. >\let:NN{\arg1}{\arg2} is particularly amusing because the first N is >\arg1 and the second one is { with an unmatched brace. One variation could be \_::, with a final ":" delimiting the argument type (\let:N: etc). It would be simpler to parse also, if the argument type should be stripped off the command name. Hans Aberg * Email: Hans Aberg * Home Page: * AMS member listing: