From: ronniec95@lineone.net
To: Daniel B?nzli <daniel.buenzli@epfl.ch>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] GC with C issues
Date: Thu, 3 Feb 2005 11:25:29 +0000 [thread overview]
Message-ID: <20050203112529.GA1820@cradle> (raw)
In-Reply-To: <1a2eef762273f70a3d436af471a1c70a@epfl.ch>
Thank you, that did the trick.
Yeah I know about the strcpy issue....but I chose to ignore it in this
test program. In this particular case, the objective is to help me be
comfortable with callbacks and the GC which is not quite working as
yet...
Ronnie
On Thu, Feb 03, 2005 at 12:06:03PM +0100, Daniel B?nzli wrote:
> When you use CAMLparam and CAMLlocal macros you must return from your C
> functions with CAMLreturn.
>
> Also, beware of your use of strcpy with String_val(aString) according
> to the documention caml strings can contain embedded null characters.
>
> Daniel
next prev parent reply other threads:[~2005-02-03 11:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 10:58 ronniec95
2005-02-03 11:06 ` [Caml-list] " Daniel Bünzli
2005-02-03 11:25 ` ronniec95 [this message]
2005-02-03 11:16 ` Olivier Andrieu
2005-02-03 11:31 ` ronniec95
2005-02-03 12:50 ` Olivier Andrieu
2005-02-03 12:52 ` Damien Doligez
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=20050203112529.GA1820@cradle \
--to=ronniec95@lineone.net \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@epfl.ch \
/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).