Received: from webgate.proteosys.de (mail.proteosys-ag.com [62.225.9.49]) by lucy.proteosys (8.11.0/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id f1JHaX104767 for ; Mon, 19 Feb 2001 18:36:33 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f1JHaXd28285 . for ; Mon, 19 Feb 2001 18:36:33 +0100 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f1JHaWH16977 for ; Mon, 19 Feb 2001 18:36:32 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C09A9A.8007A680" Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.8.57]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id SAA09676 for ; Mon, 19 Feb 2001 18:36:32 +0100 (MET) Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f1JHaVQ00274 for ; Mon, 19 Feb 2001 18:36:31 +0100 (MET) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <15.5285FBA2@mail.listserv.gmd.de>; Mon, 19 Feb 2001 18:36:23 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 490694 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 19 Feb 2001 18:36:28 +0100 Received: from ix.urz.uni-heidelberg.de (mail.urz.uni-heidelberg.de [129.206.119.234]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id SAA29868 for ; Mon, 19 Feb 2001 18:36:27 +0100 (MET) Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by ix.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id SAA46270 for ; Mon, 19 Feb 2001 18:36:27 +0100 Received: from server-11.tower-4.starlabs.net (mail.london-1.starlabs.net [212.125.75.12]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with SMTP id f1JHaRx03190 for ; Mon, 19 Feb 2001 18:36:28 +0100 (MET) Received: (qmail 15125 invoked from network); 19 Feb 2001 17:32:09 -0000 Received: from nagmx1e.nag.co.uk (HELO nag.co.uk) (62.232.54.130) by server-11.tower-4.starlabs.net with SMTP; 19 Feb 2001 17:32:09 -0000 Received: from penguin.nag.co.uk (IDENT:root@penguin.nag.co.uk [192.156.217.14]) by nag.co.uk (8.9.3/8.9.3) with ESMTP id RAA14828 for ; Mon, 19 Feb 2001 17:36:23 GMT Received: by penguin.nag.co.uk (8.9.3) id RAA04921; Mon, 19 Feb 2001 17:31:58 GMT In-Reply-To: (message from Lars =?iso-8859-1?Q?Hellstr=F6m?= on Mon, 19 Feb 2001 18:14:17 +0100) References: =?iso-8859-1?Q?=3Cl03102800b6b5fe495104=40=5B130=2E239=2E137=2E13?= =?iso-8859-1?Q?=5D=3E_=28message_from_Lars____________Hellstr=F6m_o?= =?iso-8859-1?Q?n_Mon=2C_19_Feb_2001_00=3A13=3A56_+0100=29__________?= =?iso-8859-1?Q?___=3Cl03102800b6b5fe495104=40=5B130=2E239=2E137?= =?iso-8859-1?Q?=2E13=5D=3E____________=3Cl03130302b6b700013e4b=40=5B1?= =?iso-8859-1?Q?30=2E239=2E20=2E144=5D=3E?= Return-Path: X-VirusChecked: Checked Content-class: urn:content-classes:message Subject: Re: New template macro families Date: Mon, 19 Feb 2001 18:31:58 +0100 Message-ID: <200102191731.RAA04921@penguin.nag.co.uk> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "David Carlisle" Sender: "Mailing list for the LaTeX3 project" To: "Multiple recipients of list LATEX-L" Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 3987 This is a multi-part message in MIME format. ------_=_NextPart_001_01C09A9A.8007A680 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > I think it's best not to deliberately mismatch the braces as a user = seeing > the above control sequence in an error message may easily mistake it = for error messages? latex users don't make errors do they? er, OK. So the ground rules should be (in case we need to add new internal csname types) a) use matched braces around "sub components of a name" b) ensure that if names are entered through the documented interface that even if an error results in one subcomponent name including a brace pair, that name clashes will still not occur. which leads to a structure more or less like \TP@ Sounds reasonable. David _____________________________________________________________________ This message has been checked for all known viruses by Star Internet = delivered through the MessageLabs Virus Control Centre. For further information = visit http://www.star.net.uk/stats.asp ------_=_NextPart_001_01C09A9A.8007A680 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: New template macro families

> I think it's best not to deliberately mismatch = the braces as a user seeing
> the above control sequence in an error message = may easily mistake it for

error messages? latex users don't make errors do = they?

er, OK.

So the ground rules should be (in case we need to add = new internal
csname types)

a) use matched braces around "sub components of a = name"
b) ensure that if names are entered through the = documented interface
   that even if an error results in one = subcomponent name including a
   brace pair, that name clashes will still = not occur.

which leads to a structure more or less like

\TP@<some identifying letter><one or more {} = groups >

Sounds reasonable.

David


________________________________________________________________= _____
This message has been checked for all known viruses = by Star Internet delivered
through the MessageLabs Virus Control Centre. For = further information visit
http://www.star.net.uk/stats.as= p

------_=_NextPart_001_01C09A9A.8007A680--