From: "Till Varoquaux" <till.varoquaux@gmail.com>
To: skaller <skaller@users.sourceforge.net>
Cc: "Jon Harrop" <jon@ffconsultancy.com>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] 246 constructors?
Date: Sun, 6 May 2007 22:31:48 +0200 [thread overview]
Message-ID: <9d3ec8300705061331u353f7038x720ea570f5ec4b64@mail.gmail.com> (raw)
In-Reply-To: <1178482830.4443.6.camel@rosella.wigram>
I'm guessing a patch against dypgen could prove usefull then.
Till
On 5/6/07, skaller <skaller@users.sourceforge.net> wrote:
> On Sun, 2007-05-06 at 20:50 +0100, Jon Harrop wrote:
> > On Sunday 06 May 2007 20:49, skaller wrote:
> > > I just got this message:
> > >
> > > File "dyp_parse.ml", line 492, characters 5-19461:
> > > Too many non-constant constructors -- maximum is 246 non-constant
> > > constructors
> > >
> > > Really???
> >
> > Yeah, I was hardcoding a bunch of enums for my Mathematica interpreter and got
> > that. Easiest solution is to use polymorphic variants instead. Then you have
> > clashes to worry about instead...
>
> Unfortunately (or not .. ) the file is generated by
> the dypgen parser generator..
>
> --
> John Skaller <skaller at users dot sf dot net>
> Felix, successor to C++: http://felix.sf.net
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
next prev parent reply other threads:[~2007-05-06 20:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 19:49 skaller
2007-05-06 19:50 ` [Caml-list] " Jon Harrop
2007-05-06 20:20 ` skaller
2007-05-06 20:31 ` Till Varoquaux [this message]
2007-05-06 21:05 ` skaller
2007-05-06 21:11 ` Brian Hurt
2007-05-06 21:25 ` skaller
2007-05-06 22:16 ` Tom
[not found] <20070506210912.38195BC82@yquem.inria.fr>
2007-05-07 8:21 ` Emmanuel Onzon
2007-05-07 12:29 ` skaller
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=9d3ec8300705061331u353f7038x720ea570f5ec4b64@mail.gmail.com \
--to=till.varoquaux@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.com \
--cc=skaller@users.sourceforge.net \
/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).