From: warplayer@free.fr
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Garbage Again
Date: Thu, 03 Jan 2002 16:42:01 +0100 (MET) [thread overview]
Message-ID: <1010072521.3c347bc9acfe1@imp.free.fr> (raw)
In-Reply-To: <20020103153557.B20919@pauillac.inria.fr>
> > It crashed again....
>
> Too bad. Are you really expecting the 500+ subscribers of this list
> to debug your code? Hint: there are at least two fencepost
> (off-by-one) problems in the code snippet you posted.
Okay.
But it's not like I was newbie asking for help each time it comes. In fact, I
have read many many times the full Interfacing C with OCaml documentation pages
to try to figure out what's going wrong. And spend many many ( too much ) hours
debugging. But sometimes you have to say "stop", because YES I'm having trouble
with GC and YES I'm looking for debug help on the list. Am I that stupid ?
I think that kind of GC problems can't be resolved without a solid knowledge of
the GC, especially when the existing support for interfacing with C is only few
doc pages, sometimes foggy (especially concerning globals and how to store value
from ocaml in C).
If one day I manage to understand all theses concepts, perhaps then writing a
full tutorial explaining all C/OCaml interfacing cases will be a good thing for
the OCaml community, and then this list will perhaps have more than 500
subsribers, don't you think ?
About theses fenceposts, I would be glad to have your holy flame lighning my
dark way.
Warp
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
prev parent reply other threads:[~2002-01-03 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-28 15:22 Warp
2002-01-03 14:35 ` Xavier Leroy
2002-01-03 15:42 ` warplayer [this message]
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=1010072521.3c347bc9acfe1@imp.free.fr \
--to=warplayer@free.fr \
--cc=caml-list@inria.fr \
--cc=xavier.leroy@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).