caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alain Frisch <Alain.Frisch@inria.fr>
To: Anastasia Gornostaeva <ermine@ermine.pp.ru>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] ulex+ocamlyacc
Date: Sun, 16 Jan 2005 07:13:57 +0100	[thread overview]
Message-ID: <41EA0625.5090907@inria.fr> (raw)
In-Reply-To: <20050115203822.GA62797@ermine.home>

Anastasia Gornostaeva wrote:
> Hello.
> 
> How I can combinate ocamlyacc and ulex (http://www.cduce.org/download/)
> instead of *.mll?

As long as you don't use the symbol_start-like functions from Parsing, you
can do something like:

  Parser.main (fun _ -> Lexer.token lexbuf) (Lexing.from_string "dummy")

(The ocamlyacc generated parser don't really use themselves the lexbuf 
argument...)

Hope this helps.

-- Alain


      reply	other threads:[~2005-01-16  6:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-15 20:38 ulex+ocamlyacc Anastasia Gornostaeva
2005-01-16  6:13 ` Alain Frisch [this message]

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=41EA0625.5090907@inria.fr \
    --to=alain.frisch@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=ermine@ermine.pp.ru \
    /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).