From: Shivkumar Chandrasekaran <shiv@ece.ucsb.edu>
To: caml-list@inria.fr
Subject: Fwd: [Caml-list] Unix.lseek versus Pervasives.pos
Date: Mon, 17 Mar 2003 16:28:41 -0800 [thread overview]
Message-ID: <9225A464-58D8-11D7-A8F0-000393942C76@ece.ucsb.edu> (raw)
Oops! That is pos_out not pos in the message below.
BTW, I did further experiments, and this seems to be a bug! The
behaviour I reported seems to depend on what exactly I am trying to
marshal out.
Begin forwarded message:
> From: Shivkumar Chandrasekaran <shiv@ece.ucsb.edu>
> Date: Mon Mar 17, 2003 2:45:42 PM US/Pacific
> To: caml-list@inria.fr
> Subject: [Caml-list] Unix.lseek versus Pervasives.pos
>
> Hi,
>
> Currently I am trying to handle "LargeFiles" while marshalling caml
> values and I have run into this incidental problem (nothing to do with
> LargeFile). If I open a file with "open_out_bin", write to it using
> "output_value" and then try to determine the position in the file
> using "pos", I get the correct value. However, if I use Unix.lseek > thus
>
> Unix.lseek (Unix.descr_of_out_channel fd_out) 0 Unix.SEEK_CUR
>
> I get a different value (so far always 0) than the one I get from
>
> pos fd_out
>
> The manual does not seem to help. Any advice will be appreciated.
> Thanks,
>
> --shiv--
>
> -------------------
> 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
>
--shiv--
-------------------
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:[~2003-03-18 0:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9225A464-58D8-11D7-A8F0-000393942C76@ece.ucsb.edu \
--to=shiv@ece.ucsb.edu \
--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