caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: james woodyatt <jhw@wetware.com>
Cc: Ocaml Trade <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamllex problem
Date: Fri, 05 Aug 2005 18:35:10 +1000	[thread overview]
Message-ID: <1123230910.6799.23.camel@localhost.localdomain> (raw)
In-Reply-To: <A885EC6D-313A-4938-9590-F31D773B8D5D@wetware.com>

[-- Attachment #1: Type: text/plain, Size: 729 bytes --]

On Thu, 2005-08-04 at 23:15 -0700, james woodyatt wrote:
> On 04 Aug 2005, at 18:03, skaller wrote:

> I know.  This is probably not what you're looking for.  

Not directly: I have to generate C++ code from Ocaml.
At present, this is easy -- the Ocaml is a transliteration
of the Dragon book algorithm, and the C++ is two lines
of matrix lookup.

I would like to adapt the algorithm, which is regexp -> DFA
without constructing an NFA, to add enough information
so the C++ automata can capture groups.

Whilst a lazy automaton is nice in Ocaml, it's a bit
more challenging when the compile and run time
have to be split between Ocaml and C++ ;(

-- 
John Skaller <skaller at users dot sourceforge dot net>


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-08-05  8:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-04 23:12 Jonathan Roewen
2005-08-04 23:53 ` Jonathan Roewen
2005-08-05  1:03   ` skaller
2005-08-05  5:11     ` Alain Frisch
2005-08-05  6:15     ` james woodyatt
2005-08-05  8:35       ` skaller [this message]
2005-08-05  9:15       ` Berke Durak
2005-08-05 11:05         ` skaller
2005-08-05 12:21           ` Jonathan Bryant
2005-08-05 12:39             ` David MENTRE

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1123230910.6799.23.camel@localhost.localdomain \
    --to=skaller@users.sourceforge.net \
    --cc=caml-list@inria.fr \
    --cc=jhw@wetware.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).