Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Tue, 1 Jan 2008 18:53:50 +0100 Received: by mail.proteosys.com (8.13.8/8.13.8) with ESMTP id m01HrhhQ028725 for ; Tue, 1 Jan 2008 18:53:43 +0100 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 m01HjsU9001015 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Jan 2008 18:45: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 lBVN1oRY025070; Tue, 1 Jan 2008 18:48:35 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.0) with spool id 237233 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 1 Jan 2008 18:48:35 +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 m01HmZbJ006600 for ; Tue, 1 Jan 2008 18:48:35 +0100 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id m01Hjgeb000796 for ; Tue, 1 Jan 2008 18:45:46 +0100 Received: by ug-out-1314.google.com with SMTP id 30so2848691ugc.1 for ; Tue, 01 Jan 2008 09:48:25 -0800 (PST) Received: by 10.67.32.7 with SMTP id k7mr13394854ugj.46.1199209704375; Tue, 01 Jan 2008 09:48:24 -0800 (PST) Received: from macintosh.local ( [87.60.18.122]) by mx.google.com with ESMTPS id j1sm45301791ugf.74.2008.01.01.09.48.17 (version=SSLv3 cipher=OTHER); Tue, 01 Jan 2008 09:48:21 -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> <18269.25346.697845.365250@morse.mittelbach-online.de> <281f1dab73f627993b7d112bbabf8b74@residenset.net> <18271.50750.510995.826662@morse.mittelbach-online.de> <874pe9yvk7.fsf@buckbeak.hogwarts> <87prwrt06v.fsf@buckbeak.hogwarts> Content-Transfer-Encoding: 7bit User-Agent: Opera Mail/9.25 (MacPPC) Message-ID: Date: Tue, 1 Jan 2008 18:46:16 +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: <87prwrt06v.fsf@buckbeak.hogwarts> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -102.599 () BAYES_00,USER_IN_WHITELIST X-Scanned-By: MIMEDefang 2.57 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 01 Jan 2008 17:53:50.0566 (UTC) FILETIME=[4412E860:01C84C9F] Status: R X-Status: X-Keywords: X-UID: 5145 On Fri, 28 Dec 2007 14:31:52 +0100, Andreas Matthias wrote: > Well, I am still pondering on this. How does \def:Npx fit into this > scheme? The x argument is not expanded before being passed to \edef. The x argument is expanded before being passed on the \def:Npn. Which is more or less true except currently it is implemented as a straight \edef because it would otherwise suffer from the same problems as other functions needing to go through a temporary variable in the \::x function. With the \expanded primitive in pdfTeX 1.50 we should have uniform behavior at last. > Here are some other functions I just ran across, where the x might not > be appropriate: \io_put_deferred:Nx, \io_put_term:x, \io_put_log:x, > \err_message:x, \err_latex_bug:x. These names have the same problem > as the proposed \int_set:Nx, haven't they? Most of those functions are from before eTeX was required and so now one could say the base form of many such messages was, say, \err_latex_bug:n which just outputs a message (making it literal with \unexpanded) and then there are x variants in case one wants to use the value of some variable in the output. You are pointing to an area of the code which hasn't received much attention after we started extending expl3 and it could use some cleaning up (so could our 4-day old daughter so I better look at that first! :-). Cheers, -- Morten