Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Mon, 3 Jan 2000 22:45:13 +0100 (MET) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.8.57]) by mailserver1.zdv.Uni-Mainz.DE (8.9.3+Sun/8.9.1) with ESMTP id WAA19186 for ; Mon, 3 Jan 2000 22:45:13 +0100 (MET) MIME-Version: 1.0 Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate2.zdv.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id WAA12327 for ; Mon, 3 Jan 2000 22:45:11 +0100 (MET) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF5633.D0703A80" Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <15.A2A834F9@mail.listserv.gmd.de>; Mon, 3 Jan 2000 22:45:02 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 447441 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 3 Jan 2000 22:44:04 +0100 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id WAA14695 for ; Mon, 3 Jan 2000 22:44:02 +0100 (MET) Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.8.57]) by relay.uni-heidelberg.de (8.9.1b+Sun/8.9.1) with ESMTP id WAA26316 for ; Mon, 3 Jan 2000 22:44:56 +0100 (MET) Received: from mailserver1.zdv.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate2.zdv.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id WAA12312 for ; Mon, 3 Jan 2000 22:45:05 +0100 (MET) Received: from istrati.zdv.uni-mainz.de (dialin407.zdv.Uni-Mainz.DE [134.93.175.107]) by mailserver1.zdv.Uni-Mainz.DE (8.9.3+Sun/8.9.1) with ESMTP id WAA19171 for ; Mon, 3 Jan 2000 22:45:04 +0100 (MET) Received: (from design@localhost) by istrati.zdv.uni-mainz.de (8.9.3/8.9.3) id VAA00406; Mon, 3 Jan 2000 21:15:40 +0100 In-Reply-To: References: <200001022115.WAA00533@istrati.zdv.uni-mainz.de> Return-Path: x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil]["1050" "Mon" "3" "January" "2000" "21:15:40" "+0100" "Frank Mittelbach" "frank.mittelbach@LATEX-PROJECT.ORG" nil "32" "Re: Naming conventions for template keys" "^Date:" nil nil "1" nil nil nil nil nil]nil) X-Authentication-Warning: istrati.zdv.uni-mainz.de: design set sender to design@istrati.zdv.uni-mainz.de using -f Content-class: urn:content-classes:message Subject: Re: Naming conventions for template keys Date: Mon, 3 Jan 2000 21:15:40 +0100 Message-ID: <200001032015.VAA00406@istrati.zdv.uni-mainz.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Frank Mittelbach" 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: 3491 This is a multi-part message in MIME format. ------_=_NextPart_001_01BF5633.D0703A80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hans Aberg writes: > >frank > > I will try to be frank, too, even though it sometimes can be hard. = :-) yes i do have definitely an advantage here > I can note that all suffix names are complete English words, except = -sep. > If one is inconsistent in this respect, names can be difficult to = remember. good point, but do you also have a good idea what to you instead? either = as short forms always or a long form for the other. i must confess that that i already hate writing foo-bar-baz-boolean =3D true but then one doesn't do this that often so undertstandable names could = be of some help if one is looking at some template instances. > (As everybody knows, "id" is the primitive undifferentiated part of = the > psychic apparatus that reacts blindly on a pleasure pain-level, and = was the > downfall of the Krells in the movie "Forbidden Planet".) that rather seems i have chosen the wrong suffix here as well. any other comments? perhaps not only on the sufixes but also on naming conventions for the = whole keyword name still frank ------_=_NextPart_001_01BF5633.D0703A80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Naming conventions for template keys

Hans Aberg writes:
 > >frank
 >
 > I will try to be frank, too, even though = it sometimes can be hard. :-)

yes i do have definitely an advantage here

 > I can note that all suffix names are = complete English words, except -sep.
 > If one is inconsistent in this respect, = names can be difficult to remember.

good point, but do you also have a good idea what to = you instead? either as
short forms always or a long form for the = other.

i must confess that that i already hate writing

  foo-bar-baz-boolean =3D true

but then one doesn't do this that often so = undertstandable names could be of
some help if one is looking at some template = instances.

 > (As everybody knows, "id" is the = primitive undifferentiated part of the
 > psychic apparatus that reacts blindly on a = pleasure pain-level, and was the
 > downfall of the Krells in the movie = "Forbidden Planet".)

that rather seems i have chosen the wrong suffix here = as well.

any other comments?

perhaps not only on the sufixes but also on naming = conventions for the whole
keyword name

still frank

------_=_NextPart_001_01BF5633.D0703A80--