Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Sat, 25 Oct 2008 14:25:16 +0200 Received: by mail.proteosys.com (8.13.8/8.13.8) with ESMTP id m9PCP9vD012742 for ; Sat, 25 Oct 2008 14:25:10 +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 m9PCJgim004136 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 25 Oct 2008 14:19:42 +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 m9OM16YO013429; Sat, 25 Oct 2008 14:19:35 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 46964 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sat, 25 Oct 2008 14:19:34 +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 m9OM16YI013429 for ; Sat, 25 Oct 2008 14:19:34 +0200 Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id m9PCJYDa004269 Message-ID: Date: Sat, 25 Oct 2008 14:19:34 +0200 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Joseph Wright Subject: Re: :nFT tests To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE 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.64 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 25 Oct 2008 12:25:16.0828 (UTC) FILETIME=[BCDEB5C0:01C9369C] Status: R X-Status: X-Keywords: X-UID: 5407 On Fri, 24 Oct 2008 10:43:05 +0200, Morten Høgholm wrote: >The FT variant was never meant to be heavily used - just a shuffle >variant so to speak. Given that, does the general test-creating macro need to include this variant? If it really only a very small number of cases, would it be better to create the appropriate macros on an as-used basis (and include them in the documentation)? -- Joseph Wright