From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] menhir
Date: Sat, 28 Apr 2007 22:15:28 +0100 [thread overview]
Message-ID: <200704282215.28300.jon@ffconsultancy.com> (raw)
In-Reply-To: <f8560b80704281247y44d44765h624cda8a94bc88f5@mail.gmail.com>
On Saturday 28 April 2007 20:47, Markus Mottl wrote:
> I think it wouldn't be difficult to update the compiler to use more
> efficient data structures, but it would certainly be a hell lot of
> work...
I've had a quick look at this before. Some of our compiler compilers were
causing ocamlopt to stack overflow and the problem turned out to be a pair of
mutually recursive functions in different modules of the type checkers that
were not tail recursive. I couldn't see an easy solution without rewriting
the whole thing in CPS.
Perhaps a program to convert OCaml code into CPS style would be useful?
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
The F#.NET Journal
http://www.ffconsultancy.com/products/fsharp_journal/?e
next prev parent reply other threads:[~2007-04-28 21:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 10:32 menhir skaller
2007-04-28 16:50 ` [Caml-list] menhir Francois Pottier
2007-04-28 19:47 ` Markus Mottl
2007-04-28 21:15 ` Jon Harrop [this message]
2007-04-29 4:43 ` skaller
2007-04-29 7:27 ` Christophe Raffalli
2007-05-01 15:57 ` Francois Pottier
2007-05-01 17:11 ` skaller
2007-05-01 17:34 ` Francois Pottier
2007-05-01 23:42 ` skaller
2007-05-02 5:38 ` Francois Pottier
2007-05-02 5:50 ` Francois Pottier
2007-05-02 8:41 ` skaller
2007-05-02 12:30 ` Francois Pottier
2007-05-02 16:29 ` skaller
2007-05-02 18:35 ` Francois Pottier
2007-05-03 1:30 ` skaller
2007-05-03 8:43 ` Joel Reymont
2007-05-01 17:15 ` skaller
2007-05-01 17:31 ` Francois Pottier
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=200704282215.28300.jon@ffconsultancy.com \
--to=jon@ffconsultancy.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).