Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Tue, 4 Aug 2009 13:10:09 +0200 Received: by mail.proteosys.com (8.14.3/8.14.3) with ESMTP id n74BA8DH003791 for ; Tue, 4 Aug 2009 13:10:08 +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 n74B3pHQ020203 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Aug 2009 13:03:51 +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 n74AIGu7011091; Tue, 4 Aug 2009 13:03:54 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 297130 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 4 Aug 2009 13:03:54 +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 n74B3saY011532 for ; Tue, 4 Aug 2009 13:03:54 +0200 Received: from mordell.elzevir.fr (mordell.elzevir.fr [92.243.3.74]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id n74B3nQQ006328 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 4 Aug 2009 13:03:53 +0200 Received: from roth.elzevir.fr (thue.elzevir.fr [88.165.216.11]) by mordell.elzevir.fr (Postfix) with ESMTPS id 66F0B35ECB for ; Tue, 4 Aug 2009 13:03:49 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by roth.elzevir.fr (Postfix) with ESMTP id 75BC8BFE1 for ; Tue, 4 Aug 2009 13:03:48 +0200 (CEST) User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 X-Enigmail-Version: 0.95.0 OpenPGP: url=http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x50A89B42 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Check-Skipped: Low on slaves (3) Message-ID: <4A781594.8060202@elzevir.fr> Date: Tue, 4 Aug 2009 13:03:48 +0200 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: =?ISO-8859-1?Q?Manuel_P=E9gouri=E9-Gonnard?= Subject: using expl3 for latex2e packages To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE 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: 04 Aug 2009 11:10:09.0109 (UTC) FILETIME=[20F6A050:01CA14F4] Status: R X-Status: X-Keywords: X-UID: 5809 Hi, I'm answering to some remarks of Will, but I think this discussion deserves a new thread... Will Robertson a écrit : > I would like to hope that the expl3 code gets to a state such that we > don't continue to see new packages on CTAN for performing basic > high-level "stuff". Just the other day we saw boolexpr, and there are > several string or token comparison packages. And there are several > looping packages, as well, I think. More famously, etoolbox attempts > similar goals as expl3 in a more familiar (but IMHO sometimes more > cryptic) way. > > I'm certainly not saying that the authors of such packages shouldn't be > doing what they're doing, but if it's doubling development time for > their other packages (which perform actual tasks, rather than > nuts'n'bolts) then it would be nice to consolidate some of this material. > As a package author, I could be tempted to use the expl3 "toolkit" and "philosophy" (naming conventions) right now for my new packages, but my main concern is the following: is expl3 stable enough for using it in production packages? Though I try to keep informed, I must admit I don't feel so sure. L3news02 states that "The expl3 code is now considered to be much more stable than it was before". expl3.pdf (section 6 "the *experimental* distribution") says "the interface will change". OTOH, source3 states that "The syntax conventions and functions provided are now ready for wider use." Who's right between expl3 and source3? (I assume source3, but...) Another point of concern about using expl3 is that probably we still need to use other l2e packages too, and then the syntax will be a mix and expl3 and l2e style. I wonder how to handle it (rename the functions I use with expl3-style names?). Maybe the l3 team could publish advice on how to use expl3 in l2e packages, and include clear statements about which level of stability can be expected from which module (I mean, are newer modules such as l3keyval and l3msg as stable as more basic modules). I you feel it's time for expl3 to be more widely used and start becoming the standard toolkit for LaTeX programming, maybe more communication could help. More generally, I feel too few people know about the current l3 achievements and philosophy, and this problem should be addressed. (Of course the l3 news are a good point in this direction.) Manuel. PS: just as there are projects like texworks aiming at "lowering the barrier to entry" in the TeX world for complete beginners, I think it's important to lower the barrier to entry in the l3 world for the average (or advanced, to begin with) l2e package writer.