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 f0TBl6707492 for ; Mon, 29 Jan 2001 12:47:06 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f0TBlp722266 . for ; Mon, 29 Jan 2001 12:47:51 +0100 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f0TBl5706058 for ; Mon, 29 Jan 2001 12:47:05 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C089E9.340C9900" 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 MAA29393 for ; Mon, 29 Jan 2001 12:47:04 +0100 (MET) X-MimeOLE: Produced By Microsoft Exchange V6.5 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 f0TBl4706054 for ; Mon, 29 Jan 2001 12:47:04 +0100 (MET) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <5.07F7BA3C@mail.listserv.gmd.de>; Mon, 29 Jan 2001 12:46:58 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 484312 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 29 Jan 2001 12:46:57 +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 MAA01627 for ; Mon, 29 Jan 2001 12:46:56 +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 MAA15846 for ; Mon, 29 Jan 2001 12:46:55 +0100 Received: from abel.math.umu.se (abel.math.umu.se [130.239.20.139]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f0TBkqY08596 for ; Mon, 29 Jan 2001 12:46:52 +0100 (MET) Received: from [130.239.20.144] (mac144.math.umu.se [130.239.20.144]) by abel.math.umu.se (8.9.2/8.9.2) with ESMTP id MAA04301; Mon, 29 Jan 2001 12:45:14 +0100 (CET) In-Reply-To: <14965.9157.631021.803002@istrati.zdv.uni-mainz.de> References: Return-Path: X-Sender: lars@abel.math.umu.se x-mime-autoconverted: from quoted-printable to 8bit by relay.urz.uni-heidelberg.de id MAA01628 Content-class: urn:content-classes:message Subject: Re: Templates Date: Mon, 29 Jan 2001 12:46:56 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: =?iso-8859-1?Q?Lars_Hellstr=F6m?= 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: 3655 This is a multi-part message in MIME format. ------_=_NextPart_001_01C089E9.340C9900 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 09.03 +0100 2001-01-29, Frank Mittelbach wrote: >Lars, [snip] > > It would be nice if this > > could be put in writing since you sometimes need one assignment to = be > > carried out before another (my concrete example of this is that an = instance > > key gets used in code for an `s' key). > >perhaps the above semantics could be made a formal specification though = it >would need to be checked whether this is true for all key types. As I = said my >recollection is that in the end the feeling was that we can't rely on = order >of specification (though even that would need formal specification) OK, you cannot in general assume that the container for one key value is assigned before the container for another (this wasn't what I thought = but it is probably logical if you think about what \DeclareInstance does). = This fact is probably important enough to be stressed in the documentation = (kind of "Note to people who write their own templates: You cannot make any assuptions about the order of assignments carried out by \DoParameterAssignments."). Lars Hellstr=F6m ------_=_NextPart_001_01C089E9.340C9900 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Templates

At 09.03 +0100 2001-01-29, Frank Mittelbach = wrote:
>Lars,
[snip]
> > It would be nice if this
> > could be put in writing since you sometimes = need one assignment to be
> > carried out before another (my concrete = example of this is that an instance
> > key gets used in code for an `s' = key).
>
>perhaps the above semantics could be made a = formal specification though it
>would need to be checked whether this is true for = all key types. As I said my
>recollection is that in the end the feeling was = that we can't rely on order
>of specification (though even that would need = formal specification)

OK, you cannot in general assume that the container = for one key value is
assigned before the container for another (this = wasn't what I thought but
it is probably logical if you think about what = \DeclareInstance does). This
fact is probably important enough to be stressed in = the documentation (kind
of "Note to people who write their own = templates: You cannot make any
assuptions about the order of assignments carried out = by
\DoParameterAssignments.").

Lars Hellstr=F6m

------_=_NextPart_001_01C089E9.340C9900--