caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Jim Miller" <gordon.j.miller@gmail.com>
To: caml-list@yquem.inria.fr
Subject: in and out channels into memory
Date: Sun, 9 Jul 2006 21:53:29 -0400	[thread overview]
Message-ID: <beed19130607091853p6f8553bbp5c70928d183bbe66@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 370 bytes --]

Is there a way in OCaml to read and write into memory using in and out
channels in the standard distribution?  It seems like there are functions
for converting everything else to in and out channels but I can't seem to
find anything for writing into and out of memory.  If there isn't something
already, is there a function for creating new in and out channels?

Thanks

[-- Attachment #2: Type: text/html, Size: 397 bytes --]

             reply	other threads:[~2006-07-10  1:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10  1:53 Jim Miller [this message]
2006-07-10  9:48 ` [Caml-list] " Richard Jones

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=beed19130607091853p6f8553bbp5c70928d183bbe66@mail.gmail.com \
    --to=gordon.j.miller@gmail.com \
    --cc=caml-list@yquem.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).