Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Wed, 9 Jul 2003 19:48:55 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h69HmrPP021428 for ; Wed, 9 Jul 2003 19:48:53 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay.uni-heidelberg.de (8.12.9/8.12.9) with ESMTP id h69HYmmp010226; Wed, 9 Jul 2003 19:34:49 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C34642.5DAE5D80" Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id h68M02qf007911; Wed, 9 Jul 2003 19:34:40 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 1829 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 9 Jul 2003 19:34:40 +0200 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.12.3/8.12.3/SuSE Linux 0.6) with ESMTP id h69HYeM9019934 for ; Wed, 9 Jul 2003 19:34:40 +0200 Received: from mail.npc.de (fw.npc.de [62.225.140.214]) by relay2.uni-heidelberg.de (8.12.9/8.12.9) with ESMTP id h69HYgGl000070 for ; Wed, 9 Jul 2003 19:34:43 +0200 (MET DST) Received: by mail.npc.de (Postfix, from userid 1014) id D6D431533; Wed, 9 Jul 2003 19:34:41 +0200 (CEST) In-Reply-To: <20030709121008.A11602@diabolo.informatik.rwth-aachen.de> References: <3F075002.72955C93@MartinHensel.de> <3F09CB24.7195F5E7@MartinHensel.de> <16138.9008.870309.967543@zarniwoop.ms25.local> <200307081028.19280.tim@birdsnest.maths.tcd.ie> <16139.118.62805.453383@puma.npc.de> <20030709121008.A11602@diabolo.informatik.rwth-aachen.de> Return-Path: X-Mailer: VM 7.04 under 21.4 (patch 8) "Honest Recruiter" XEmacs Lucid X-OriginalArrivalTime: 09 Jul 2003 17:48:55.0544 (UTC) FILETIME=[5E015F80:01C34642] X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -19.8 () IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES Content-class: urn:content-classes:message Subject: Re: Invitation for discussion: My suggestion for a LaTeX3 syntax Date: Wed, 9 Jul 2003 18:34:41 +0100 Message-ID: A<16140.21041.677628.264047@pussy.npc.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: Invitation for discussion: My suggestion for a LaTeX3 syntax Thread-Index: AcNGQl4vjgxFsI30RR2SaT0YS9HmWA== From: "Joachim Schrod" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4668 This is a multi-part message in MIME format. ------_=_NextPart_001_01C34642.5DAE5D80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable >>>>> "AB" =3D=3D Achim Blumensath = writes: AB> On the other hand, the advantage of using OCaml is that every = command AB> has access to all internals of ant. AB> I'm thinking of implementing a special purpose programming language = for AB> style files, but that's a lot of work and I won't manage to make it = as AB> fast as compiled OCaml code. So probably I'll just write a = preprocessor AB> to add some syntactic sugar to OCaml. I haven't seen a better real-world illustration why real macro systems (like in Dylan, Common Lisp, or Scheme) are a Good Thing(tm). They allow to enhance the base language to get exactly that functionality. I'll keep that example. ;-) Joachim -- =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D Joachim Schrod Email: jschrod@acm.org Roedermark, Germany ``How do we persuade new users that spreading fonts across the = page like peanut butter across hot toast is not necessarily the route = to typographic excellence?'' -- Peter Flynn ------_=_NextPart_001_01C34642.5DAE5D80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Invitation for discussion: My suggestion for a LaTeX3 = syntax

>>>>> "AB" =3D=3D Achim = Blumensath <blume@I7.INFORMATIK.RWTH-AACHEN.DE> writes:

AB> On the other hand, the advantage of using OCaml = is that every command
AB> has access to all internals of ant.

AB> I'm thinking of implementing a special purpose = programming language for
AB> style files, but that's a lot of work and I = won't manage to make it as
AB> fast as compiled OCaml code. So probably I'll = just write a preprocessor
AB> to add some syntactic sugar to OCaml.

I haven't seen a better real-world illustration why = real macro systems
(like in Dylan, Common Lisp, or Scheme) are a Good = Thing(tm). They
allow to enhance the base language to get exactly = that functionality.
I'll keep that example. ;-)

        = Joachim

--
=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D
Joachim = Schrod           &= nbsp;           &n= bsp;          Email: = jschrod@acm.org
Roedermark, Germany

        ``How do we = persuade new users that spreading fonts across the page
        like = peanut butter across hot toast is not necessarily the route to
        = typographic = excellence?''          =              = -- Peter Flynn

------_=_NextPart_001_01C34642.5DAE5D80--