caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gregoire Sutre <sutre@ic.EECS.Berkeley.EDU>
To: caml-list@inria.fr
Cc: Rupak Majumdar <rupak@ic.EECS.Berkeley.EDU>
Subject: [Caml-list] OCaml/C++ : STL conflicts
Date: Sun, 22 Apr 2001 10:58:12 -0700	[thread overview]
Message-ID: <20010422105812.A24638@ic.EECS.Berkeley.EDU> (raw)

Hi,

I would like to use a C++ library in an OCaml program.  Fortunately, the
linking problems were solved quite easily:

(1) declaring each external C++ function as extern "C"
(2) enlosing the caml/* includes inside an extern "C"
(3) specifying the C++ compiler with the -cc option of ocamlc/ocamlopt

But I have not tested thoroughly yet.  Do you believe that there might be
problems with this approach?

Regarding (2) above, I was by the way surprised that the caml/* header
files did not use the usual construct:

#ifdef __cplusplus
extern "C" {
#endif

-------------------
To unsubscribe, mail caml-list-request@inria.fr.  Archives: http://caml.inria.fr


                 reply	other threads:[~2001-04-23 11:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010422105812.A24638@ic.EECS.Berkeley.EDU \
    --to=sutre@ic.eecs.berkeley.edu \
    --cc=caml-list@inria.fr \
    --cc=rupak@ic.EECS.Berkeley.EDU \
    /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).