X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["2030" "Fri" "11" "February" "1994" "15:39:00" "+0100" "Frank Poppe" "POPPE@swov.nl" "<199402111440.AA26470@mail.cs.tu-berlin.de>" "37" "Re: On compatibility in LaTeX2e [was: Re: keyed options lis" "^Date:" nil nil "2" "1994021114:39:00" "On compatibility in LaTeX2e [was: Re: keyed options lis" nil nil]) Return-Path: Received: from sc.ZIB-Berlin.DE (mailserv) by dagobert.ZIB-Berlin.DE (4.1/SMI-4.0/24.6.93) id AA21901; Fri, 11 Feb 94 15:41:08 +0100 Received: from mail.cs.tu-berlin.de by sc.ZIB-Berlin.DE (4.1/SMI-4.0-sc/03.06.93) id AA08174; Fri, 11 Feb 94 15:40:08 +0100 Received: from tubvm.cs.tu-berlin.de by mail.cs.tu-berlin.de with SMTP id AA26470 (5.65c8/IDA-1.4.4(mail.m4[1.12]) for <@MAIL.CS.TU-BERLIN.DE:Schoepf@SC.ZIB-BERLIN.DE>); Fri, 11 Feb 1994 15:40:03 +0100 Message-Id: <199402111440.AA26470@mail.cs.tu-berlin.de> Received: from TUBVM.CS.TU-BERLIN.DE by tubvm.cs.tu-berlin.de (IBM VM SMTP V2R2) with BSMTP id 3612; Fri, 11 Feb 94 15:39:51 +0200 Received: from VM.URZ.UNI-HEIDELBERG.DE (NJE origin MAILER@DHDURZ1) by TUBVM.CS.TU-BERLIN.DE (LMail V1.2a/1.8a) with BSMTP id 3611; Fri, 11 Feb 1994 15:39:49 +0200 Received: from VM.URZ.UNI-HEIDELBERG.DE (NJE origin LISTSERV@DHDURZ1) by VM.URZ.UNI-HEIDELBERG.DE (LMail V1.2a/1.8a) with BSMTP id 4119; Fri, 11 Feb 1994 15:39:08 +0000 Reply-To: Mailing list for the LaTeX3 project Date: Fri, 11 Feb 1994 15:39:00 +0100 From: Frank Poppe Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: On compatibility in LaTeX2e [was: Re: keyed options lis Status: R X-Status: X-Keywords: X-UID: 1543 Rainer Schoepf : RS> Coming back to the proposal above for LaTeX3, namely using the syntax RS> RS> \command[[key1]value1[key2]value2]{required} RS> RS> this is a problem as you cannot have TeX grab everything between RS> matching pairs of square brackets, only between [ and the next ]. RS> That leaves only the hand-crafted argument scanning mechanism, which RS> might lead to a performance problem. This statement is very tentative, RS> we haven't actually tried this, so I can't say that this is much RS> slower. RS> RS> On the other hand, I find the syntax with the equal sign easier to RS> understand. The only possible incompatibility is if an optional RS> argument in the current system would contain an equal sign. However, RS> that is very unlikely, as most optional arguments are either from a RS> fixed set [thb], or of a fixed type (e.g., a length). \documentclass RS> and \usepackage seem to be the only exception, plus any new command RS> that a package might possibly define. This cannot be ruled out RS> completely, but I think that package writers are not likely to invent RS> options with equal signs in them. RS> I agree that the key=value syntax is easier to understand. But remember that this line of discussion started with the wish to have more optional commands on the \section command: the ability to specfify different texts for t-o-c and mark's, apart from the section title to appear in the text. The chance that somebody would want to use an equal sign may not be great, but shouldn't be ignored either. _____________________________________________________________________________ Frank Poppe tel: +31 70 3209323 Institute for Road Safety Research SWOV fax: +31 70 3201261 ,,, ,, ,, ,, .... ,, ,, mail: PO Box 170 ||,,, || || || :: :: || || 2260 AD Leidschendam ,,,|~ ||,'|,~ :: :' ||,~ the Netherlands