caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Mikhail Fedotov <mikhail@kittown.com>
To: "Jean-Baptiste Rouquier" <Jean-Baptiste.Rouquier@inrialpes.fr>
Cc: caml-list@inria.fr
Subject: Re[2]: [Caml-list] interfacing C and OCaml
Date: Fri, 27 Jun 2003 12:59:56 +0400	[thread overview]
Message-ID: <21255847.20030627125956@kittown.com> (raw)
In-Reply-To: <015e01c33c86$e06b79d0$7115c7c2@inrialpes.fr>

Hello Jean-Baptiste,

Friday, June 27, 2003, 12:31:44 PM, you wrote:

>> JBR> 1. Should I use
>> JBR> CAMLprim value input(value channel, value buffer, value offset, value
>> JBR> length)
>> JBR> {
>> JBR>   return Val_long (...);
>> JBR> }
>>
>> Yes. This function can be called from other C function or from OCaml.
>>
>> JBR> as in 18.1.2 in the manual, or
>>
>> JBR> void foo (value v1, value v2, value v3)
>> JBR> {
>> JBR> CAMLparam3 (v1, v2, v3);
>> JBR> ...
>> JBR> CAMLreturn0;
>> JBR> }
>>
>> This if for functions called from C only. Not suitable for use from
>> OCaml directly.
>>
>> Should be specified in the manual, I believe, but I've got no response
>> in the list to my comment on this. I hope it will be in the manual for
>> the OCaml 3.07.
>>


JBR> Strange !
JBR> The complete example given in 18.6 contains :

JBR> curses.mli :
JBR> external initscr: unit -> window = "curses_initscr"

JBR> curses.c ("curses.o" in the manual) :
JBR> value curses_initscr(value unit)
JBR> {
JBR> CAMLparam1 (unit);
JBR> CAMLreturn ((value) initscr());
JBR> }

JBR> curses.ml :
JBR> open Curses
JBR> let main_window = initscr () in


JBR> So functions using CAMLparam and CAMLreturn are called from OCaml directly.
JBR> Or am I completely wrong ?
JBR> I'm worried about the GC (for now, my code seems to run correctly, but use
JBR> perhaps to much memory).

Sorry, I've made a mistake myself. I've been talking mostly about "void" vs "value"
issue in your examples, but this is already addressed in the manual by stating that
the primitive function must return value. The documentation lacks introduction into
the macroses "CAMLprim", "CAMLextern" etc, but they are not strictly required now
if you are not dealing with Windows DLLs.

I'd say that it is a bad style to write code without those macroses,
at least.

-- 
Best regards,
 Mikhail                            mailto:mikhail@kittown.com

-------------------
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-06-27  8:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-26 14:42 Jung Woon Ho
2003-06-26 15:14 ` Lex Stein
2003-06-26 19:02 ` Jean-Baptiste Rouquier
2003-06-27  5:24   ` Re[2]: " Mikhail Fedotov
2003-06-27  8:31     ` Jean-Baptiste Rouquier
2003-06-27  8:59       ` Mikhail Fedotov [this message]
2003-06-27 12:57         ` Re[2]: " art yerkes
2003-06-27 13:14           ` Re[4]: " Mikhail Fedotov
2003-06-27 17:45             ` art yerkes

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=21255847.20030627125956@kittown.com \
    --to=mikhail@kittown.com \
    --cc=Jean-Baptiste.Rouquier@inrialpes.fr \
    --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;
as well as URLs for NNTP newsgroup(s).