X-VM-v5-Data: ([nil nil nil nil t nil nil nil nil] ["646" "Thu" "10" "February" "1994" "20:16:12" "GMT" "Sebastian Rahtz" "spqr@FTP.TEX.AC.UK" "<199402102024.AA00749@mail.cs.tu-berlin.de>" "14" "Re: On compatibility in LaTeX2e [was: Re: keyed options lists]" "^Date:" nil nil "2" "1994021020:16:12" "On compatibility in LaTeX2e [was: Re: keyed options lists]" nil "<9402101448.AA12508@ftp.tex.ac.uk>"]) Return-Path: Received: from sc.ZIB-Berlin.DE (mailserv) by dagobert.ZIB-Berlin.DE (4.1/SMI-4.0/24.6.93) id AA18462; Thu, 10 Feb 94 21:24:25 +0100 Received: from mail.cs.tu-berlin.de by sc.ZIB-Berlin.DE (4.1/SMI-4.0-sc/03.06.93) id AA04382; Thu, 10 Feb 94 21:24:24 +0100 Received: from tubvm.cs.tu-berlin.de by mail.cs.tu-berlin.de with SMTP id AA00749 (5.65c8/IDA-1.4.4(mail.m4[1.12]) for <@MAIL.CS.TU-BERLIN.DE:Schoepf@SC.ZIB-BERLIN.DE>); Thu, 10 Feb 1994 21:24:22 +0100 Message-Id: <199402102024.AA00749@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 6225; Thu, 10 Feb 94 21:22:37 +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 6224; Thu, 10 Feb 1994 21:22:37 +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 1529; Thu, 10 Feb 1994 21:22:07 +0000 Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <9402101448.AA12508@ftp.tex.ac.uk> Date: Thu, 10 Feb 1994 20:16:12 GMT From: Sebastian Rahtz Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: On compatibility in LaTeX2e [was: Re: keyed options lists] Status: R X-Status: X-Keywords: X-UID: 1530 Philip TAYLOR writes: > paragraph: what possible `syntax rules laid down for LaTeX2' can affect > the syntax of a new primitive such as \documentclass? Surely the > specifier of a new primitive is entitled to specify the syntax of such, > as well as its semantics? its a question of avoiding anti-social behaviour, no more, no less. its been obvious to me since 1985 what the unwritten rules for LaTeX are, and I would no more write a user-level macro for a LaTeX package that used ^M as a delimiter for end of argument that I would light a bonfire on washing day, or talk about Mornington Crescent on an international list :-} Sebastian