Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Mon, 10 Dec 2007 11:36:21 +0100 Received: by mail.proteosys.com (8.13.8/8.13.8) with ESMTP id lBAAaFqk004293 for ; Mon, 10 Dec 2007 11:36:15 +0100 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 lBAATsbA015228 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Dec 2007 11:29:54 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id lB9N1KFK008751; Mon, 10 Dec 2007 11:29:46 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.0) with spool id 215112 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 10 Dec 2007 11:29:46 +0100 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 lBAATkYh005395 for ; Mon, 10 Dec 2007 11:29:46 +0100 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id lBAARY9P019562 for ; Mon, 10 Dec 2007 11:27:37 +0100 Received: by ug-out-1314.google.com with SMTP id 30so1679717ugc for ; Mon, 10 Dec 2007 02:29:36 -0800 (PST) Received: by 10.67.116.15 with SMTP id t15mr5881448ugm.1197282576010; Mon, 10 Dec 2007 02:29:36 -0800 (PST) Received: from gdhcp88.gbar.dtu.dk ( [192.38.95.88]) by mx.google.com with ESMTPS id 30sm6906913ugf.2007.12.10.02.29.33 (version=SSLv3 cipher=OTHER); Mon, 10 Dec 2007 02:29:34 -0800 (PST) Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 References: <87k5nxw76i.fsf@buckbeak.hogwarts> <87tzmwkdnr.fsf@buckbeak.hogwarts> Content-Transfer-Encoding: 8bit User-Agent: Opera Mail/9.24 (MacPPC) Message-ID: Date: Mon, 10 Dec 2007 11:29:31 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: =?iso-8859-1?Q?Morten_H=F8gholm?= Subject: Re: Misleading cs names? 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: -2.599 () BAYES_00 X-Scanned-By: MIMEDefang 2.57 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 10 Dec 2007 10:36:21.0526 (UTC) FILETIME=[8156C360:01C83B18] Status: R X-Status: X-Keywords: X-UID: 5109 On Sun, 09 Dec 2007 22:33:12 +0100, Lars Hellström wrote: Hi Lars, > 9 dec 2007 kl. 20.14 skrev Morten Høgholm: >> >> So perhaps an alternative could be to use something like >> \int_set:Nr {expression}% r for register? >> >> Opinions? > > How would such an r be different from x? Technically there wouldn't be any difference of course. Only the implication that everywhere else, x means there is also an n base function, which is also more or less why I chose the n form initially. We have umpteen different expansion designations (leading my thoughts to a Commodores song which is a sign of me not getting enough sleep and/or coffee) and I know adding an extra is not helping that situation either. I am happy to get comments from expert users such as you and Matthias so we can make it work the way you'd expect. >> It should be clear from the documentation what is expandable and what >> is not. > > Is that a state that the LaTeX3 sources is currently supposed to be in, > or not? One thing that *irritated* me when reading a bit of it last week > was that it frequently wasn't clear whether something was expandable or > not, and for many things that is something that I'd need to know. As you say, it is irritating not to know whether or not a function is expandable and it is something I would very much like to change. Soon. I suggested: >> Something like what Heiko does in zref? How would you like it to appear? It'd be fine by me if the sources were changed to something such as % \begin{function}{ % \csexp{clist_map_function:NN} % \csexp{clist_map_function:cN} % \csexp{clist_map_function:nN} % } % \begin{function}{ % \cs{clist_map_inline:Nn} % \cs{clist_map_inline:cn} % \cs{clist_map_inline:nn} % } or similar. [...] > No need to go that far for examples. \csname ... \endcsname should be > obvious to all, and you can play quite a lot of tricks with \number as > well. Currently we are well on our way to MI ways of using \romannumeral and some are due to the lack of \expanded. Others are just very useful for space trimming. > Another important expandable primitive doing full expansion (as far as > it needs to) is \if, which is used in docstrip to implement evaluation > of guard expressions yes, \if is good for tricks as well. > (in particular there was really no need for the eTeX \unless primitive, > since \if could already be used to negate conditions). I never quite saw the big advantage either, especially because you can't just do \def\whatever#1#2{\ifx#1#2equal\else not\fi} \unless\whatever Cheers, -- Morten