Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Yaron Minsky" <yminsky@cs.cornell.edu>
To: "Sebastien Ferre" <ferre@irisa.fr>
Cc: caml-list@yquem.inria.fr, "Daniel Bünzli" <daniel.buenzli@epfl.ch>
Subject: Re: [Caml-list] marshaling limits
Date: Wed, 17 Jan 2007 14:50:23 -0500	[thread overview]
Message-ID: <891bd3390701171150m601bb382ufc1d05f088281b93@mail.gmail.com> (raw)
In-Reply-To: <45AE5001.2080709@irisa.fr>

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

Don't quote me on this, but I believe that marshal uses a string in bytecode
with threads, uses straight malloc with bytecode and no threads, and never
uses strings in native code.  I'm /very/ unsure about that last one, but I
am pretty confident that in some cases, whether it uses strings depends on
whether threads are involved.

y

On 1/17/07, Sebastien Ferre <ferre@irisa.fr> wrote:
>
>
> Daniel Bünzli wrote:
>
> >> pourtant, je passe bien par un appel a output_value
> >> dans un fichier, sans passer par une chaine intermediaire.
> >
> > Maybe output_value uses a string internally. Try with a bytecode
> > version of your executable, an exception should be raised (or have a
> > look at the implementaiton of output_value).
>
> I used a bytecode version.
>
> I checked the code of output_value, and it uses an internal
> string. So it won't work.
>
> Anyway, I knew I would have to go for a more serious
> solution as soon as data get really large. I think of
> using something like GDBM.
>
> Thanks for the help.
> Sebastien
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>

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

  parent reply	other threads:[~2007-01-17 19:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-16 20:48 ocaml+twt v0.90 Mike Lin
2007-01-17  9:14 ` marshaling limits Sebastien Ferre
2007-01-17  9:36   ` [Caml-list] " Olivier Andrieu
2007-01-17 15:33   ` Frédéric Gava
2007-01-17 15:41     ` Sebastien Ferre
2007-01-17 16:12       ` Daniel Bünzli
2007-01-17 16:32         ` Olivier Andrieu
2007-01-18  8:14           ` Sebastien Ferre
2007-01-17 16:34         ` Sebastien Ferre
2007-01-17 19:37           ` Jonathan Roewen
2007-01-17 19:50           ` Yaron Minsky [this message]
2007-01-17 22:51             ` Markus Mottl
2007-01-23 20:43 ` [Caml-list] ocaml+twt v0.90 Ingo Bormuth
     [not found]   ` <2a1a1a0c0701231322h48e3af00m9f07371f236fe7c@mail.gmail.com>
2007-01-24 16:09     ` Ingo Bormuth

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=891bd3390701171150m601bb382ufc1d05f088281b93@mail.gmail.com \
    --to=yminsky@cs.cornell.edu \
    --cc=caml-list@yquem.inria.fr \
    --cc=daniel.buenzli@epfl.ch \
    --cc=ferre@irisa.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