caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Erik de Castro Lopo <ocaml-erikd@mega-nerd.com>
To: <caml-list@inria.fr>
Subject: Re: [Caml-list] yacc style
Date: Fri, 28 Jan 2005 13:28:12 +1100	[thread overview]
Message-ID: <20050128132812.7001512c.ocaml-erikd@mega-nerd.com> (raw)
In-Reply-To: <1106874879.12114.145.camel@pelican.wigram>

On 28 Jan 2005 12:14:39 +1100
skaller <skaller@users.sourceforge.net> wrote:

> On Fri, 2005-01-28 at 08:39, Erik de Castro Lopo wrote:
> >
> > Yes, normally the parser generates a parse tree which is then
> > passed to the semantic analyser for semantic checking.
> 
> Unfortunately this is useless in the common case
> of needing to parse C.

I'm happy to take your word for it John, but I'd like to know
why.

> It would surely be nice
> to be able to pass an argument to ocamlyacc,
> as can now be done for ocamllex.

Could you give a example?

> Strangely in this case the ideal place to add
> on  the typedef table would be the lexbuf,

Ok, so this enables you to know at lex time if an identifier is 
a user type avoiding ugly parser hacks to work around the fact
that identifier X is actually a user defined type.

Am I on the right track here?

Erik
-- 
+-----------------------------------------------------------+
  Erik de Castro Lopo  nospam@mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
"life is too long to know C++ well" -- Erik Naggum


  reply	other threads:[~2005-01-28  2:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-27 20:17 Chris King
2005-01-27 21:39 ` [Caml-list] " Erik de Castro Lopo
2005-01-28  1:14   ` skaller
2005-01-28  2:28     ` Erik de Castro Lopo [this message]
2005-01-28  4:30       ` skaller
2005-01-28  9:04       ` Jean-Christophe Filliatre
     [not found] ` <200501272252.43720.jon@jdh30.plus.com>
2005-01-28  0:41   ` Chris King

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=20050128132812.7001512c.ocaml-erikd@mega-nerd.com \
    --to=ocaml-erikd@mega-nerd.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;
as well as URLs for NNTP newsgroup(s).