Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Tue, 25 Jan 2000 22:52:13 +0100 (MET) 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 WAA16012 for ; Tue, 25 Jan 2000 22:52: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 WAA29084 for ; Tue, 25 Jan 2000 22:52:11 +0100 (MET) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF677E.6FDDA480" Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <14.3E9EE571@mail.listserv.gmd.de>; Tue, 25 Jan 2000 22:51:56 +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 449805 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Tue, 25 Jan 2000 22:50:44 +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 WAA09566 for ; Tue, 25 Jan 2000 22:50:42 +0100 (MET) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.8.56]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.3) with ESMTP id WAA03614 for ; Tue, 25 Jan 2000 22:50:43 +0100 (MET) Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate1.zdv.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id WAA15385 for ; Tue, 25 Jan 2000 22:52:06 +0100 (MET) Received: from istrati.zdv.uni-mainz.de (root@dialin376.zdv.Uni-Mainz.DE [134.93.175.76]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id WAA16001 for ; Tue, 25 Jan 2000 22:52:06 +0100 (MET) Received: (from design@localhost) by istrati.zdv.uni-mainz.de (8.9.3/8.9.3) id VAA02276; Tue, 25 Jan 2000 21:27:01 +0100 In-Reply-To: References: <200001251342.OAA01742@istrati.zdv.uni-mainz.de> Return-Path: x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil]["1038" "Tue" "25" "January" "2000" "21:27:01" "+0100" "Frank Mittelbach" "frank.mittelbach@LATEX-PROJECT.ORG" nil "25" "Re: template interfaces and what they mean" "^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: template interfaces and what they mean Date: Tue, 25 Jan 2000 21:27:01 +0100 Message-ID: <200001252027.VAA02276@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: 3510 This is a multi-part message in MIME format. ------_=_NextPart_001_01BF677E.6FDDA480 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hans, > -- Perhaps this input can be used for the template discussion: > > One idea that comes to my mind in connection with the "environments = with > hooks" is to build up two layers, one which takes care of the = semantics, > and one which takes of the syntax by which the environments are = called. not really since I was talking only about the semantic layer; what you = propose is (under a different label) the separation as it is provided by the = interface of xparse on one hand (syntax side) and the template on the other hand (semantics) but what i was getting at is that the semantics layer need further clarification (and they would in your code as well the question isn't different there) > Here, some arguments should (when required by the environment = definition) > be passed to the commands \/before, \/begin, \/end, i was trying to pin down the nature of those "some arguments" this was = the question posed in the thread not whether or not separation of syntax and semantics is helpful/sensible. frank ------_=_NextPart_001_01BF677E.6FDDA480 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: template interfaces and what they mean

Hans,

 > -- Perhaps this input can be used for the = template discussion:
 >
 > One idea that comes to my mind in = connection with the "environments with
 > hooks" is to build up two layers, one = which takes care of the semantics,
 > and one which takes of the syntax by which = the environments are called.

not really since I was talking only about the semantic = layer; what you propose
is (under a different label) the separation as it is = provided by the interface
of xparse on one hand (syntax side) and the template = on the other hand
(semantics)

but what i was getting at is that the semantics layer = need further
clarification (and they would in your code as well = the question isn't
different there)

 > Here, some arguments should (when required = by the environment definition)
 > be passed to the commands = \<name>/before, \<name>/begin, \<name>/end,

i was trying to pin down the nature of those = "some arguments" this was the
question posed in the thread not whether or not = separation of syntax and
semantics is helpful/sensible.

frank

------_=_NextPart_001_01BF677E.6FDDA480--