Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Mon, 27 Apr 2009 13:31:28 +0200 Received: by mail.proteosys.com (8.14.3/8.14.3) with ESMTP id n3RBVQRI030372 for ; Mon, 27 Apr 2009 13:31:26 +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 n3RBNcNP012761 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Apr 2009 13:23:38 +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 n3R9l6G4028614; Mon, 27 Apr 2009 13:23:28 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 275019 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 27 Apr 2009 13:23:28 +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 n3RBNSvt031702 for ; Mon, 27 Apr 2009 13:23:28 +0200 Received: from mordell.elzevir.fr (mordell.elzevir.fr [92.243.3.74]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id n3RBNDls006554 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Mon, 27 Apr 2009 13:23:17 +0200 Received: from roth.elzevir.fr (thue.elzevir.fr [88.165.216.11]) by mordell.elzevir.fr (Postfix) with ESMTPS id 69616359E9 for ; Mon, 27 Apr 2009 13:23:13 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by roth.elzevir.fr (Postfix) with ESMTP id 1F0BCBFCF for ; Mon, 27 Apr 2009 13:23:12 +0200 (CEST) User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 References: <20090424092120.GA7843@irwin.vpn.uni-freiburg.de> <5.1.0.14.0.20090421122917.02f41830@pop3.web.de> <455691F1-21A4-4C65-A025-7855791829F7@gmail.com> <20090424092120.GA7843@irwin.vpn.uni-freiburg.de> <5.1.0.14.0.20090425151542.032a0ce0@pop3.web.de> <20090425183703.GA2822@irwin.vpn.uni-freiburg.de> 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 Message-ID: <49F5959F.5070104@elzevir.fr> Date: Mon, 27 Apr 2009 13:23:11 +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: Re: \in@ wrong? To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <20090425183703.GA2822@irwin.vpn.uni-freiburg.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: 27 Apr 2009 11:31:29.0016 (UTC) FILETIME=[B4F3AF80:01C9C72B] Status: R X-Status: X-Keywords: X-UID: 5770 Heiko Oberdiek a écrit : >> (This uses \@nil.) Putting the second split into a macro to test it against >> \@empty is safe, but one might dislike it as "slow". > > I prefer "safe". > I agree. > An expandable test could be used, e.g.: > \ifx\\##2\\% or something else as \\ Is it "allowed" to use e-TeX commands inside the kernel? If so, \expandafter\ifx\expandafter\\\detokenize{##2}\\% or something else as \\ is the safest test, as I'm sure you know. Anyway, depending on the intended use of \in@, certain resctrictions (such as "no unbalanced \if" or "no # token" or "no \@nil token" are probably acceptable, as long as they are properly documented. Manuel.