From: Ken Wakita <wakita-private@is.titech.ac.jp>
To: Brian Hurt <brian.hurt@qlogic.com>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Ocamllex/Ocamlyacc feature request
Date: Thu, 29 May 2003 19:16:14 +0900 [thread overview]
Message-ID: <941EB0B0-91BE-11D7-B411-000393B9096C@is.titech.ac.jp> (raw)
In-Reply-To: <Pine.LNX.4.33.0305281557180.32567-100000@eagle.ancor.com>
You can turn the parser trace facility on by:
setenv OCAMLRUNPARAM "p"
Read the OCAMLRUNPARAM section in:
http://caml.inria.fr/ocaml/htmlman/manual024.html
Ken Wakita
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-05-29 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 21:03 Brian Hurt
2003-05-29 10:16 ` Ken Wakita [this message]
2003-05-29 12:03 ` Damien
2003-05-29 13:07 ` Luc Maranget
2003-06-04 9:19 ` [Caml-list] Syntax error Lukasz Lew
2003-06-04 17:25 ` Stefan Heimann
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=941EB0B0-91BE-11D7-B411-000393B9096C@is.titech.ac.jp \
--to=wakita-private@is.titech.ac.jp \
--cc=brian.hurt@qlogic.com \
--cc=caml-list@inria.fr \
/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