Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Tue, 18 Aug 2009 01:59:58 +0200 Received: by mail.proteosys.com (8.14.3/8.14.3) with ESMTP id n7HNxv8X005682 for ; Tue, 18 Aug 2009 01:59:58 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id n7HNtWq8001693 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Aug 2009 01:55:33 +0200 Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id n7HM1lfO029448; Tue, 18 Aug 2009 01:55:22 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 283818 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 18 Aug 2009 01:55:21 +0200 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id n7HNtLlV004877 for ; Tue, 18 Aug 2009 01:55:21 +0200 Received: from rv-out-0708.google.com (rv-out-0708.google.com [209.85.198.250]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id n7HNtRIa005508 for ; Tue, 18 Aug 2009 01:55:31 +0200 Received: by rv-out-0708.google.com with SMTP id c5so792753rvf.10 for ; Mon, 17 Aug 2009 16:55:16 -0700 (PDT) Received: by 10.141.4.20 with SMTP id g20mr2519480rvi.121.1250553316225; Mon, 17 Aug 2009 16:55:16 -0700 (PDT) Received: from ?10.0.1.105? (122-49-156-202.ip.adam.com.au [122.49.156.202]) by mx.google.com with ESMTPS id k37sm386067rvb.27.2009.08.17.16.55.12 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 17 Aug 2009 16:55:14 -0700 (PDT) References: ,<1C09237E-F871-434B-9527-4C6A3F2CF6A0@gmail.com> <4A852C0B.8080608@elzevir.fr> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (7A341) Mime-Version: 1.0 (iPhone Mail 7A341) X-Spam-Whitelist: Message-ID: <026FA2E8-5889-4146-9854-262A2574F057@gmail.com> Date: Tue, 18 Aug 2009 09:25:04 +0930 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Will Robertson Subject: Re: Named parameters in macros To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -6.599 () BAYES_00,RCVD_IN_DNSWL_MED X-Scanned-By: MIMEDefang 2.65 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 17 Aug 2009 23:59:58.0403 (UTC) FILETIME=[D34C5130:01CA1F96] Status: R X-Status: X-Keywords: X-UID: 5937 (Sent from my phone. Apologies for brevity.) On 18/08/2009, at 0:38, "J.Fine" wrote: > Manuel wrote: > >>> Thank you. It's not the only nice thing we can do. Here are some >>> more: >>> >>> * Allow digits in control sequence names >>> * Allow period in control sequence names >> >> I think the naming scheme (at the programming level at leat) has been >> discussed >> previously and is now considered stable. Let's not re-discuss again >> and >> again >> points were decisions are already made. (And btw, I personnaly >> think the >> namign >> scheme in expl3 is good.) > > My suggestion is compatible with the LaTeX3 naming scheme. Did you > think it was not? Period (I think) and digits (definitely) must all be catcode other to work inside numexpr and so on. I wish it were otherwise, but I don't think it's nice to have to use scantokens to sanitise input for all numeric work. > >>> * Allow '~' to produce a space /in all circumstances/ >>> >> What would be the purpose? > > So that > \this ~ \that > has as space between \this and \that, for example. Or to get > several spaces in a row. ~ is currently catcode space in expl3 since space itself is catcode ignore. So I don't think this suggestion is feasible either. Will