Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Sat, 22 Aug 2009 18:01:05 +0200 Received: by mail.proteosys.com (8.14.3/8.14.3) with ESMTP id n7MG14So000936 for ; Sat, 22 Aug 2009 18:01:04 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id n7MFtuTm015156 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 22 Aug 2009 17:55:56 +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 n7MCXLmm029540; Sat, 22 Aug 2009 17:55:47 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 287532 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sat, 22 Aug 2009 17:55:47 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id n7MFtlvQ008701 for ; Sat, 22 Aug 2009 17:55:47 +0200 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id n7MFtgnC021027 for ; Sat, 22 Aug 2009 17:55:46 +0200 Received: from morse.mittelbach-online.de (p54A83E1C.dip.t-dialin.net [84.168.62.28]) by mrelayeu.kundenserver.de (node=mrbap2) with ESMTP (Nemesis) id 0MKt72-1MeswQ2YQB-000C5e; Sat, 22 Aug 2009 17:55:42 +0200 Received: by morse.mittelbach-online.de (Postfix, from userid 501) id AE5096EF8D; Sat, 22 Aug 2009 17:55:39 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <4A7921CF.5020803@morningstar2.co.uk> <4A8EC449.4040509@morningstar2.co.uk> X-Mailer: VM 7.19 under Emacs 21.3.1 X-Provags-ID: V01U2FsdGVkX18N+garfi8YUj8gjVw5b5o49nXJMPH3vIDFTH6 uR/EwazSbQfMRHOZoMHlzGqL05sAtXfX8xtrjtfqgvUWdhEsgR xPuJw723jijdxzspUY8Rg== X-Spam-Whitelist-Provider: Message-ID: <19088.5371.517713.176151@morse.mittelbach-online.de> Date: Sat, 22 Aug 2009 17:55:39 +0200 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Frank Mittelbach Subject: Re: xparse To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <4A8EC449.4040509@morningstar2.co.uk> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -106.599 () BAYES_00,RCVD_IN_DNSWL_MED,USER_IN_WHITELIST X-Scanned-By: MIMEDefang 2.65 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 22 Aug 2009 16:01:05.0098 (UTC) FILETIME=[C0FAAAA0:01CA2341] Status: R X-Status: X-Keywords: X-UID: 5976 Now after this excure in layers ... ... coming back to xparse: to a large extent that implentation provided one possible incarnation of a document-level user interface modeled after current 2e, in other words it was meant to provide a user interface in which you can define user commands that look like current 2e commands and offer the same kind of possibilities (like a * or optional arguments present by [...]) It should therefore probably be better named xparse-2e or something like that. After all, it is a) quite possible to envsion more than one document level interface being available in parallel b) a 2e-like interface, while needed to allow supporting 2e documents is not necessarily the best interface for the future c) depending on requirements and environment on that level interfaces might make use of additional tools to manage the input stream if we accept that the current xparse is really xparse-2e (whether we call it that or not) then one consequence from this for me is that xparse-2e should offer the possibility to define commands with a syntax that fits current 2e. I would expect that once we have a clearer picture of how to do the separation between layer -1 and layer 0 all this needs rewriting anyway I also hope (and expect) that once we are clear on how to write specifications for layer 0 properly, that other interfaces for layer -1 will be written, both because more than one might be needed and because we need some trials to settle on what we want to promote as that standard layer -1 for latex3 frank