From: Michel Schinz <Michel.Schinz@epfl.ch>
To: caml-list@inria.fr
Subject: Re: Why can't I use val mover : < move : int -> unit; .. > list -> unit ?
Date: 11 Jan 2001 13:26:43 +0100 [thread overview]
Message-ID: <yorselyal1fg.fsf@lamppc2.epfl.ch> (raw)
In-Reply-To: "Mattias Waldau"'s message of "Thu, 11 Jan 2001 10:07:33 +0100"
"Mattias Waldau" <mattias.waldau@tacton.se> writes:
[...]
> Also, I would be interested in how Ocaml can make the call within
> main and mover to move efficiently. Other static compiled
> OO-languages use vtables, but I don't see how Ocaml can use a
> vtable. How expensive are these methods calls? There are no numbers
> of this in the Ocaml-FAQ
Jérôme Vouillon wrote a message in this list once to explain the
dispatching technique used in OCaml. The message is archived there:
http://pauillac.inria.fr/~doligez/caml-guts/objects.txt
Michel.
next prev parent reply other threads:[~2001-01-11 17:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 12:39 Mattias Waldau
2001-01-10 19:16 ` Brian Rogoff
2001-01-11 9:07 ` Mattias Waldau
2001-01-11 12:26 ` Michel Schinz [this message]
2001-01-11 13:09 ` Sylvain BOULM'E
2001-01-10 19:58 ` Alain Frisch
2001-01-11 9:29 ` Sylvain BOULM'E
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=yorselyal1fg.fsf@lamppc2.epfl.ch \
--to=michel.schinz@epfl.ch \
--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).