X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1086" "Fri" "10" "September" "1999" "18:09:18" "+0100" "James Kilfiger" "mapdn@CSV.WARWICK.AC.UK" nil "25" "Re: xparse" "^Date:" nil nil "9" nil "xparse" nil nil nil] nil) Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mail.Uni-Mainz.DE (8.8.8/8.8.8) with ESMTP id TAA01193 for ; Fri, 10 Sep 1999 19:09:24 +0200 (MET DST) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <3.7583E26C@mail.listserv.gmd.de>; Fri, 10 Sep 1999 19:09:24 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 444553 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Fri, 10 Sep 1999 19:09:21 +0200 Received: from daffodil.csv.warwick.ac.uk (daffodil.csv.warwick.ac.uk [137.205.192.30]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id TAA04891 for ; Fri, 10 Sep 1999 19:09:19 +0200 (MET DST) Received: from mimosa.csv.warwick.ac.uk (mapdn@mimosa [137.205.192.34]) by daffodil.csv.warwick.ac.uk (8.9.3/8.9.3) with ESMTP id SAA23782 for ; Fri, 10 Sep 1999 18:09:19 +0100 (BST) Received: (from mapdn@localhost) by mimosa.csv.warwick.ac.uk (8.9.3/8.9.3) id SAA26622; Fri, 10 Sep 1999 18:09:18 +0100 (BST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-ID: <199909101709.SAA26622@mimosa.csv.warwick.ac.uk> Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <199909101556.QAA21090@nag.co.uk> from David Carlisle at "Sep 10, 99 04:56:53 pm" Date: Fri, 10 Sep 1999 18:09:18 +0100 From: James Kilfiger Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: xparse Status: R X-Status: X-Keywords: X-UID: 3322 > I wrote: > > One feature which I think would be nice is a \newargumenttype macro, > > analogous to \newcolumntype of the array package. David writes: > What new sorts of argument would you want. (this is a real question > so I understand the functionality you are asking for) Well three thoughts I had: Using characters other than * to indicate variant forms. I can imagine a command with two independent variants, accesed by \foo, \foo*, \foo+, and \foo*+ If one wanted to make a `3d' picture mode, a triplet (x,y,z) argument might be useful. It is proposed that the float placement argument be in the form [hb|tp]; this might be a convienent form for other commands. Here my inventivness begins to run-out. Perhaps these are bad ideas; too many argument types will only cause confusion for the user. But I can imagine a \newargtype scheme being useful. Other thing, making the default value of an optional command the same as that of another command, as is done with \@dblarg, I can imagine \DeclareDocumentCommand{\foo}{m O{#1}}{...} being useful. James