caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Rafael 'Dido' Sevilla" <dido@imperium.ph>
To: ocaml_beginners@yahoogroups.com
Subject: [Caml-list] parsing forward references in ocamlyacc and other ocamlyacc questions
Date: Wed, 3 Sep 2003 13:31:14 +0800	[thread overview]
Message-ID: <20030903053114.GA2490@imperium.ph> (raw)

I'm just wondering how you can guarantee that certain imperative effects
occur, like adding a name into a symbol table hash.  I'm writing a
compiler whose semantics allow some limited forward references, e.g.:

adt_declaration: IDENTIFIER COLON ADT OBRACE adt_member_list CBRACE SEMI

where the rules under the adt_member_list nonterminal have access to the
identifier name given in the ADT declaration.  For the original Yacc or
Bison, it can be done with an intermediate semantic action like:

adt_declaration: IDENTIFIER COLON ADT { Hashtbl.add symtable $1 ... } OBRACE ...

Something like (which is how you would do it without the use of
intermediate actions):

adt_name: IDENTIFIER COLON ADT { Hashtbl.add symtable $1 adt_skel; $1 }
  ;

adt_declaration: adt_name OBRACE adt_member_list CBRACE SEMI { ... }
  ;

doesn't seem to work.  The symbol table addition still doesn't occur
until after the entire adt_declaration has been parsed.  The
documentation for ocamlyacc has very little to say about it (unless
there's more documentation in other places besides the ocaml manual).

I'll also ask how I would go about processing file inclusion in
ocamlyacc using ocamllex...

-------------------
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-05  9:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-03  5:31 Rafael 'Dido' Sevilla [this message]
2003-09-05 12:07 ` Eckart Goehler
2003-09-05 20:56 ` Michal Moskal

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=20030903053114.GA2490@imperium.ph \
    --to=dido@imperium.ph \
    --cc=ocaml_beginners@yahoogroups.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).