caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jean Krivine <jean.krivine@gmail.com>
To: Xavier Leroy <Xavier.Leroy@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Array.make exception and parser
Date: Wed, 5 Jan 2011 14:46:03 +0100	[thread overview]
Message-ID: <AANLkTikkPGn8eLCvtxJdRYiFHgJwC89J9jTjp-i8g-41@mail.gmail.com> (raw)
In-Reply-To: <4D247425.9070400@inria.fr>

Good point. I think the fundamental reason is my poor grammar. But I
guess this should deserve a better warning that an Invalid_argument in
my face :)

Thanks!

On Wed, Jan 5, 2011 at 2:37 PM, Xavier Leroy <Xavier.Leroy@inria.fr> wrote:
> On 01/04/2011 02:41 PM, Jean Krivine wrote:
>
>> I am encountering a weird problem, I am trying to parse a very large
>> file (around 1.2 GB) according to a grammar defined in ocamlyacc.
>> During the parsing I get the exception
>> Invalid_argument "Array.make".
>> This  is strange because I am not using any array.
>
> As others said, you're just overflowing the stack of the parse engine.
>
> As no one else said already, watch out for left recusion vs. right
> recursion in your grammar, esp. the rules matching long sequences.  For more
> details, see e.g.
>
> http://tldp.org/HOWTO/Lex-YACC-HOWTO-6.html
>
> section 6.2, or many compiler textbooks.
>
> - Xavier Leroy
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa-roc.inria.fr/wws/info/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>


      reply	other threads:[~2011-01-05 13:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04 13:41 Jean Krivine
2011-01-04 14:56 ` Daniel Bünzli
2011-01-04 14:57   ` Daniel Bünzli
2011-01-04 14:57 ` Török Edwin
2011-01-04 15:14   ` Jean Krivine
2011-01-04 15:31     ` Daniel Bünzli
2011-01-04 16:22       ` Yitzhak Mandelbaum
2011-01-04 16:42         ` Daniel Bünzli
2011-01-04 17:03           ` Yitzhak Mandelbaum
2011-01-04 17:04       ` Jean Krivine
2011-01-04 17:22         ` Daniel Bünzli
2011-01-04 15:38     ` bluestorm
2011-01-04 17:43       ` Jean Krivine
     [not found]       ` <1125074892.441923.1294163043602.JavaMail.root@zmbs2.inria.fr>
2011-01-04 17:53         ` Francois Pottier
     [not found]     ` <1259991756.440008.1294155536392.JavaMail.root@zmbs2.inria.fr>
2011-01-04 17:45       ` Francois Pottier
2011-01-04 19:30         ` Daniel Bünzli
2011-01-04 19:52           ` Yitzhak Mandelbaum
2011-01-04 20:36             ` Daniel Bünzli
     [not found]         ` <1263353434.442766.1294169448342.JavaMail.root@zmbs2.inria.fr>
2011-01-04 20:31           ` Francois Pottier
2011-01-04 20:40             ` Lukasz Stafiniak
2011-01-04 21:03               ` Török Edwin
2011-01-05  3:24                 ` Yitzhak Mandelbaum
2011-01-05 14:12             ` Boris Yakobowski
2011-01-05 21:12             ` Boris Yakobowski
2011-01-05 13:37 ` Xavier Leroy
2011-01-05 13:46   ` Jean Krivine [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=AANLkTikkPGn8eLCvtxJdRYiFHgJwC89J9jTjp-i8g-41@mail.gmail.com \
    --to=jean.krivine@gmail.com \
    --cc=Xavier.Leroy@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).