From: "Warp" <warplayer@free.fr>
To: "OCaml" <caml-list@inria.fr>
Subject: [Caml-list] Bug value
Date: Tue, 19 Feb 2002 13:13:59 +0100 [thread overview]
Message-ID: <00f901c1b93e$e95ad6c0$3c00a8c0@warp> (raw)
Is the following code :
let read_fdata file =
let id = (input_value file : fid) in
let infos = (input_value file : finfos) in
{
id = id;
infos = infos;
childs = clist;
deps = dlist;
}
equivalent to :
let read_fdata file =
{
id = (input_value file : fid);
infos = (input_value file : finfos);
}
?
Because the first one got no problem while the second one is causing a fatal
bug at run-time when I try to access the struct
PS :
-----
type fid = int
type fver = int
type ftype = int
type finfos = {
mutable name : string;
mutable parent : fid;
mutable ver : fver;
mutable t : ftype;
}
Warp
-------------------
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
next reply other threads:[~2002-02-19 12:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 12:13 Warp [this message]
2002-02-19 12:43 ` Dmitry Lomov
2002-02-19 14:35 ` Sven
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='00f901c1b93e$e95ad6c0$3c00a8c0@warp' \
--to=warplayer@free.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).