This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C02F9A.496D1FB2 Content-Type: text/plain; charset="ISO-8859-1" > > > > Mark> What (quasi-)parser to use? Current candidates are > to adapt MinML, to > > Mark> wait for Monty's fixes to ANTLR, or to just write > a Minimal-XML > > Mark> quasi-parser by hand. > > > >I think writing one by hand is a bad idea. Better, in my > mind, to wait for > >Monty's fixes or adapt MinML and publish the adaptions > > Monty, any ETA? Between the holiday crush at work (mail-order company) and treatment for my tendonitis, I'd realistically say Jan/Feb :( Monty ------_=_NextPart_001_01C02F9A.496D1FB2 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">RE: [E-Lang] Kernel-E in Minimal-XML >
>
> > Mark> What = (quasi-)parser to use? Current candidates are
> to adapt MinML, to
> > Mark> wait for = Monty's fixes to ANTLR, or to just write
> a Minimal-XML
> > Mark> quasi-parser by = hand.
> >
> >I think writing one by hand is a bad idea. = Better, in my
> mind, to wait for
> >Monty's fixes or adapt MinML and publish = the adaptions
>
> Monty, any ETA?Between the holiday crush at work (mail-order = company) and treatment for my tendonitis, I'd realistically say Jan/Feb = :(
Monty
------_=_NextPart_001_01C02F9A.496D1FB2--