Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Tue, 11 Aug 2009 23:25:11 +0200 Received: by mail.proteosys.com (8.14.3/8.14.3) with ESMTP id n7BLP8Lx030914 for ; Tue, 11 Aug 2009 23:25:08 +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 n7BLL3ZG021831 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Aug 2009 23:21:03 +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 n7BJ3J4H028140; Tue, 11 Aug 2009 23:21:02 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 295889 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 11 Aug 2009 23:21:02 +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 n7BLL27i013621 for ; Tue, 11 Aug 2009 23:21:02 +0200 Received: from av6-1-sn3.vrr.skanova.net (av6-1-sn3.vrr.skanova.net [81.228.9.179]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id n7BLKtxt008370 for ; Tue, 11 Aug 2009 23:20:58 +0200 Received: by av6-1-sn3.vrr.skanova.net (Postfix, from userid 502) id 6352B3805A; Tue, 11 Aug 2009 23:20:54 +0200 (CEST) Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net [81.228.9.101]) by av6-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 457C837EE6 for ; Tue, 11 Aug 2009 23:20:54 +0200 (CEST) Received: from Kuben.local (90-230-192-94-no86.tbcn.telia.com [90.230.192.94]) by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 1C20837E4B for ; Tue, 11 Aug 2009 23:20:54 +0200 (CEST) User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605) MIME-Version: 1.0 References: <4A816AD5.30303@elzevir.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id n7BLL27i013622 Message-ID: <4A81E0B6.4010209@residenset.net> Date: Tue, 11 Aug 2009 23:20:54 +0200 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: =?ISO-8859-1?Q?Lars_Hellstr=F6m?= Subject: Re: remarks on expl3.pdf To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <4A816AD5.30303@elzevir.fr> 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: 11 Aug 2009 21:25:11.0703 (UTC) FILETIME=[3583DA70:01CA1ACA] Status: R X-Status: X-Keywords: X-UID: 5893 Manuel Pégourié-Gonnard skrev: > Hi, > > Here are some remarks from my last reading of expl3.pdf (r1439). > > 1. Concerning the terminology of "functions". Maybe it's worth mentioning at > some point that the word function is used in opposition to variable, not to > macro: theses two objects (functions and variables) remain actually macros, and > TeX a macro language (like make or C preprocessor as opposed to C). Currently, I > expect only experienced TeX programmers will look into expl3 so they should be > mistaken, but for the TeX-programming newcomer, the peculiarities of a macro > language are often so difficult to understand, that IMO expl3 should state > clearly that it doesn't magically turn TeX into a classical programming > language, and that the terms function/variable are only a convention, an not to > be understood in their usual meaning. Hear, hear! d-(^_^)-b > 2. Still terminology: sometimes "execution" is used when the most accurate term > would be expansion (eg on the top of page 7). Again, I expect an experienced TeX > programmer to understand what is actually meant, but I think that for the sake > of less experienced readers, such language approximations should be avoided, or > the document should include a warning that sometimes "execution" will be used as > a generic term for execution-or-expansion-or-both. I'd certainly expect "execution" to mean "this may involve doing things in the stomach". Lars Hellström