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 f07F3Yp03972 for ; Sun, 7 Jan 2001 16:03:34 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f07F3l700596 . for ; Sun, 7 Jan 2001 16:03:47 +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 f07F3XM00212 for ; Sun, 7 Jan 2001 16:03:34 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C078BB.01282700" 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 QAA02935 for ; Sun, 7 Jan 2001 16:03:33 +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 f07F3W011881 for ; Sun, 7 Jan 2001 16:03:32 +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 <2.D8A6D6C6@mail.listserv.gmd.de>; Sun, 7 Jan 2001 16:03:32 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 478224 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sun, 7 Jan 2001 16:03: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 QAA03358 for ; Sun, 7 Jan 2001 16:02: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 QAA24036 for ; Sun, 7 Jan 2001 16:02:57 +0100 Received: from musse.tninet.se (musse.tninet.se [195.100.94.12]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with SMTP id f07F2oU12031 for ; Sun, 7 Jan 2001 16:02:53 +0100 (MET) Received: (qmail 24274 invoked from network); 7 Jan 2001 16:02:35 +0100 Received: from garibaldi.tninet.se (HELO algonet.se) (195.100.94.103) by musse.tninet.se with SMTP; 7 Jan 2001 16:02:35 +0100 Received: from [195.100.226.131] (du131-226.ppp.su-anst.tninet.se [195.100.226.131]) by garibaldi.tninet.se (BLUETAIL Mail Robustifier 2.2.1) with ESMTP id 42267.879754.978garibaldi-s0 ; Sun, 07 Jan 2001 16:02:34 +0100 In-Reply-To: <14935.39414.219844.570581@spqr2.oucs.ox.ac.uk> References: <200101061950.OAA03845@pluto.math.albany.edu> <200101061950.OAA03845@pluto.math.albany.edu> Return-Path: X-Sender: haberg@pop.matematik.su.se Content-class: urn:content-classes:message Subject: Re: GELLMU progress Date: Sun, 7 Jan 2001 16:01:25 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Hans Aberg" 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: 3645 This is a multi-part message in MIME format. ------_=_NextPart_001_01C078BB.01282700 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 22:19 +0000 1-01-06, Sebastian Rahtz wrote: >at a minimum, you have to get a flex patched to handle Unicode; it >exists, but its not standard. Please give a reference (URL) to Unicode Flex. -- I am myself thinking of patching up Bison so that it can do Unicode parsing. The drawback with this approach is that it is more complicated = to write regular words, but one anyhow has access to the more general LR(1) grammars that Bison can handle. From the practical point of view, developing Flex and Bison synched together proves difficult, because they belong to different = organizations: Bison is maintained by GNU with a public development policy; Flex by somebody else, and I have not heard of any public development of Flex = for the last couple years. >you *can* write an XML parser in flex, >as Richard Goerwitz has demonstrated, but its not trivial. I would not use Flex for doing the actual parsing, only to recognize lexemes. Flex just recognizes regular words which can be turned on/off = by some context switches (called "start-conditions").These Flex context switches are useful in connection with Bison, becuase one can use them = to handle language context dependencies. Hans Aberg ------_=_NextPart_001_01C078BB.01282700 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: GELLMU progress

At 22:19 +0000 1-01-06, Sebastian Rahtz wrote:
>at a minimum, you have to get a flex patched to = handle Unicode; it
>exists, but its not standard.

Please give a reference (URL) to Unicode Flex.

-- I am myself thinking of patching up Bison so that = it can do Unicode
parsing. The drawback with this approach is that it = is more complicated to
write regular words, but one anyhow has access to the = more general LR(1)
grammars that Bison can handle.

>From the practical point of view, developing Flex = and Bison synched
together proves difficult, because they belong to = different organizations:
Bison is maintained by GNU with a public development = policy; Flex by
somebody else, and I have not heard of any public = development of Flex for
the last couple years.

>you *can* write an XML parser in flex,
>as Richard Goerwitz has demonstrated, but its not = trivial.

I would not use Flex for doing the actual parsing, = only to recognize
lexemes. Flex just recognizes regular words which can = be turned on/off by
some context switches (called = "start-conditions").These Flex context
switches are useful in connection with Bison, becuase = one can use them to
handle language context dependencies.

  Hans Aberg

------_=_NextPart_001_01C078BB.01282700--