caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Benjamin Geer <ben@socialtools.net>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: [Caml-list] parsing included files recursively using ocamllex and ocamlyacc
Date: Sat, 20 Sep 2003 15:38:22 +0100	[thread overview]
Message-ID: <3F6C665E.5030508@socialtools.net> (raw)

I'm writing an interpreter for a small language (to be released as an 
open source library), using ocamllex and ocamlyacc.  I'd like this 
language to support an instruction that, at compile time, recursively 
includes source code from another file.

I searched the list archives and found a message 
(http://pauillac.inria.fr/caml/caml-list/0258.html), posted here in 1997 
by Xavier Leroy, which suggests one way to write a recursive 
"yacc_start" function.  However, the details of this approach aren't 
clear to me; could someone provide a more detailed explanation of what 
would be involved (e.g. a brief outline of the contents of this 
function)?  What about ocamllex?  Would I have to save the lexbuf on a 
stack, and restore it after each recursive call?

I considered using (or writing) a preprocessor to do the includes, but I 
couldn't think of a way to do this without losing the ability to report 
filenames and line numbers in run-time error messages.

Ben


-------------------
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


             reply	other threads:[~2003-09-20 14:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-20 14:38 Benjamin Geer [this message]
2003-09-20 15:15 ` Michal Moskal
2003-09-20 19:07   ` Benjamin Geer
2003-09-22  7:22     ` Eckart Goehler
2003-09-22  8:41 ` Hendrik Tews

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=3F6C665E.5030508@socialtools.net \
    --to=ben@socialtools.net \
    --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;
as well as URLs for NNTP newsgroup(s).