caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Damien Doligez <Damien.Doligez@inria.fr>
To: "Caml-List" <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamlyacc bug?
Date: Tue, 22 Apr 2003 16:28:57 +0200	[thread overview]
Message-ID: <C0C4E0A0-74CE-11D7-B39E-0003930FCE12@inria.fr> (raw)
In-Reply-To: <002101c30895$52410cd0$fe00a8c0@hama>

On Tuesday, April 22, 2003, at 08:06 AM, SooHyoung Oh wrote:

> Is the following an ocamlyacc bug?

No.  At worst, it is a misfeature that results in an unclear error
message.

> When making application with using ocamlyacc + ocamllex,
> you can make main function in trailer part (after second "%%") of 
> "foo.mly"
> It that case, it generates an error like this:
>     This expression has type Lexing.lexbuf -> Eg_parse.token
>     but is here used with type Lexing.lexbuf -> token

The problem in your source, is that you add your main function at
the end of the parser.  But this function uses the lexer, so you
make Eg_parse depend on Eg_lex.  But the design of ocamllex/ocamlyacc
is that the parser is declaring the type of tokens, and the lexer
opens the parser module to use this declaration, so it is Eg_lex
that depends on Eg_parse.

By adding your main function at the end of eg_parse.ml, you make a
circular dependency between eg_parse and eg_lex.  You should add your
main function at the end of eg_lex instead.

-- Damien

-------------------
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-04-22 14:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22  6:06 SooHyoung Oh
2003-04-22 14:28 ` Damien Doligez [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=C0C4E0A0-74CE-11D7-B39E-0003930FCE12@inria.fr \
    --to=damien.doligez@inria.fr \
    --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).