From: Xavier Leroy <xavier.leroy@inria.fr>
To: Brian Naylor <bwv211mail@yahoo.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] inconsistent assumptions over interface . . .
Date: Mon, 19 Aug 2002 10:19:09 +0200 [thread overview]
Message-ID: <20020819101909.D31368@pauillac.inria.fr> (raw)
In-Reply-To: <20020815225500.97586.qmail@web13409.mail.yahoo.com>; from bwv211mail@yahoo.com on Thu, Aug 15, 2002 at 03:55:00PM -0700
> How can I free myself of the "inconsistent assumptions" error? My micro test
> case has the following:
This exposes a bug in the implementation of "-pack" in OCaml 3.05.
Expect a fix in 3.06.
- Xavier Leroy
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2002-08-19 8:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 22:55 Brian Naylor
2002-08-19 8:19 ` Xavier Leroy [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=20020819101909.D31368@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=bwv211mail@yahoo.com \
--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).