From: skaller <skaller@users.sourceforge.net>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: 246 constructors?
Date: Mon, 07 May 2007 05:49:13 +1000 [thread overview]
Message-ID: <1178480953.4443.4.camel@rosella.wigram> (raw)
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???
(The file is generated by dypgen, it has a constructor for
every terminal and non-terminal in the Felix grammar)
At least on a 64 bit machine this is a sad restriction:
any chance of a two byte code here?
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next reply other threads:[~2007-05-06 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 19:49 skaller [this message]
2007-05-06 19:50 ` [Caml-list] " Jon Harrop
2007-05-06 20:20 ` skaller
2007-05-06 20:31 ` Till Varoquaux
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
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=1178480953.4443.4.camel@rosella.wigram \
--to=skaller@users.sourceforge.net \
--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).