caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: caml-list <caml-list@inria.fr>
Subject: [Caml-list] file close bug?
Date: 28 Jun 2004 02:21:19 +1000	[thread overview]
Message-ID: <1088353277.32642.28.camel@pelican.wigram> (raw)

The following code has worked for some time:

try (* to write Marshalled parse tree out *)
  let x = open_out_bin pf in
  Marshal.to_channel x (this_version,sts) [];
  close_out x
with _ -> () (* can't write, don't worry *)

Now, I have modified my program to use some specialised
hashtable types using address comparisons on part of the keys.
My largest test case now fails to terminate (weird!, it worked
before with polymorphic comparison ..) but I can kill it with Ctrl-C.

What's weird is that if I rerun it, it tries to reload
the Marshalled data above, and gets an End_of_file error,
indicating the whole file was not written out. 

However,when I run another program which doesn't get up to 
the use of the new hashtbles, and so terminates, the whole
file *is* being correctly written out (by the same piece of code).

This looks like a flushing/closing problem in Ocaml?
[Just because the program aborted should not prevent
a *closed* file's buffers being written to disk ..]

There's been some talk about this in other circumstances?
Is this a known problem?

-- 
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850, 
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net



-------------------
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


             reply	other threads:[~2004-06-27 16:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-27 16:21 skaller [this message]
2004-06-27 16:33 ` skaller
2004-06-27 16:45   ` skaller
2004-06-27 19:04     ` William Lovas
2004-06-27 19:42       ` skaller
2004-06-27 20:15         ` Jon Harrop
2004-06-28  1:10           ` 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=1088353277.32642.28.camel@pelican.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).