caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Christophe Raffalli <christophe.raffalli@univ-savoie.fr>
To: Damien Doligez <damien.doligez@inria.fr>,
	Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>,
	Issac Trotts <ijtrotts@rni.org>
Cc: caml-list <caml-list@inria.fr>
Subject: [Caml-list] Calback (was caml_oldify_local_roots taking too much time)
Date: Tue, 20 Jul 2004 16:00:57 -0400	[thread overview]
Message-ID: <40FD79F9.6040309@univ-savoie.fr> (raw)
In-Reply-To: <3B84CC2A-D97E-11D8-A7B0-00039310CAE8@inria.fr>

Thanks for the help on the list. I decided to change Glut.timerFunc for 
the following code, passing the Caml function and its argument using a C 
int (transmitted to the times) which is in fact a pointer to a Caml 
pair. This pointer is registered as a global root and removed by the 
callback itself. I give the code bellow if someone wants to write 
something similar.

A small question: why do people use callback trough a name and a 
hashtable instead of passing the callback inside C variables (global or 
local) ? It could save a lot of time ?

For instance Glut.idleFunc will do a search in the hashtable of caml 
names at each callback and if the callback was transmitted  through a C 
global variable there vould only be one indirection ?

I am about to change all the callback mechnism used in Glut. So if 
anyone knows a good reason to use names and hashtables ?

----- 8< ----- here is the code

----- First the caml code:


(* timerFunc is non-window-dependent *)
external _glutTimerFunc : int->((value:'a->'b) * 'a)->unit = 
"ml_glutTimerFunc"
let timerFunc ~ms ~cb ~value:v : (unit) =
     _glutTimerFunc ms (cb,v);; (* register the callback with GLUT *)

----- Then the C code:


--
// for timer we can not use Register.callback because it grows 
infinitely the
// number of global root

static void glutTimerFunc_cb(int fun_arg)
{
   // fun_arg is a pointer on a caml pair hidden in an integer.
   // Moreover we remove the global root because each callback is used once
   // by the timer.
   value *v = (value) fun_arg;
   leave_blocking_section ();
   value fun = Field(*v, 0);
   value arg = Field(*v, 1);
   caml_remove_global_root(v);
   free(v);
   callback (fun, arg);
   enter_blocking_section ();
}

CAMLprim value ml_glutTimerFunc(value millis_val, value fun_arg) // set 
Timer callback
{
   // fun_arg is a caml pair with a function and its argument we 
register a root on this pair and set the callback.
     unsigned int millis;
     value *v = (value*) malloc(sizeof(value));
     *v = fun_arg;
     caml_register_global_root(v);
     millis = Int_val(millis_val);
     glutTimerFunc(millis, &glutTimerFunc_cb, (int) v); // register with 
GLUT
     return Val_unit;
}

--
Christophe Raffalli
Université de Savoie
Batiment Le Chablais, bureau 21
73376 Le Bourget-du-Lac Cedex

tél: (33) 4 79 75 81 03
fax: (33) 4 79 75 87 42
mail: Christophe.Raffalli@univ-savoie.fr
www: http://www.lama.univ-savoie.fr/~RAFFALLI
---------------------------------------------
IMPORTANT: this mail is signed using PGP/MIME
At least Enigmail/Mozilla, mutt or evolution
can check this signature
---------------------------------------------

-------------------
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


  parent reply	other threads:[~2004-07-20 14:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-19 17:59 [Caml-list] GC and caml_oldify_local_roots taking too much time Christophe Raffalli
2004-07-19 12:21 ` Damien Doligez
2004-07-19 19:33   ` Christophe Raffalli
2004-07-19 20:17   ` Christophe Raffalli
2004-07-19 14:28     ` Richard Jones
2004-07-19 14:38       ` Richard Jones
2004-07-19 15:12     ` Olivier Andrieu
2004-07-19 20:36   ` Christophe Raffalli
2004-07-20 20:00   ` Christophe Raffalli [this message]
2004-07-20 14:40     ` [Caml-list] Calback Olivier Andrieu
     [not found]       ` <40FD9FDE.3070000@univ-savoie.fr>
2004-07-20 22:44         ` Christophe Raffalli
2004-07-21  0:54           ` Jere Sanisalo
2004-07-20 23:09       ` Christophe Raffalli

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=40FD79F9.6040309@univ-savoie.fr \
    --to=christophe.raffalli@univ-savoie.fr \
    --cc=caml-list@inria.fr \
    --cc=damien.doligez@inria.fr \
    --cc=garrigue@kurims.kyoto-u.ac.jp \
    --cc=ijtrotts@rni.org \
    /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).