caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jonathan Roewen <jonathan.roewen@gmail.com>
To: caml-list@yquem.inria.fr
Subject: [Caml-list] parsers/lexers some more
Date: Sun, 11 Sep 2005 04:12:47 +1200	[thread overview]
Message-ID: <ad8cfe7e05091009123069af23@mail.gmail.com> (raw)

Hi Again,

I'm having a problem with my native code version of my parser/lexer
combo. I've tested it in the top-level, and it works fine.

However, with my OS, the ocaml runtime causes a processor exception
(normally a bounds check error).

I'm curious: is the lexer & parser C code exactly the same for both
bytecode & native code versions? I'm finding it hard to understand why
it works in bytecode, and not in my OS.

Also, I've noticed that ocaml exceptions aren't propogated correctly
in my OS iff it's from parsing/lexing. Any insights on what could
cause that?

Jonathan


                 reply	other threads:[~2005-09-10 16:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ad8cfe7e05091009123069af23@mail.gmail.com \
    --to=jonathan.roewen@gmail.com \
    --cc=caml-list@yquem.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).