From: Ravi Chamarty <ravi@ittc.ukans.edu>
To: caml-list@inria.fr
Subject: [Caml-list] Caml Wrappers
Date: Wed, 7 Mar 2001 17:58:28 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.10.10103071749420.9499-100000@elroy.ittc.ukans.edu> (raw)
Hi ,
I am trying to write OCaml interfaces around a C library. I tried
looking at the Unix library and trying to understand it. However, I have
much complex data types to deal with.I was wondering if anyone could help
me out.
Here is a signature of one of the C functions:
an_flow_t *
an_flow_create(void *mem, an_cred_t *cred, an_cpuspec_t *cspec,
an_memspec_t *mspec, an_flowinit_func_t init,
void *initarg, an_flowterm_func_t term)
Each of these types are complex structures in C. How do I represent these
in OCaml. Is it useful to use classes and methods? Or do I use abstract
types to represent them ?
An example of one of these structures is given below:
struct an_flow_t {
struct hnode me; /* flow hier link (must be first) */
struct ani_cred *cred; /* credentials */
struct ani_mempool *mpool; /* mempool */
struct ani_chan *chanlist; /* list of channels */
struct ani_threadpool tpool; /* thread pool */
int flags; /* various flags */
an_flowterm_func_t termfunc; /* termination function */
ani_resource_t res; /* reserved resources */
int refs; /* reference count */
ani_ilock_t lock; /* mutual exclusion */
an_flowstats_t stats; /* statistics */
};
I would be grateful for any help.
Thanks
Ravi
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next reply other threads:[~2001-03-07 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-07 23:58 Ravi Chamarty [this message]
2001-03-08 2:39 ` Jacques Garrigue
2001-03-08 8:45 ` Jocelyn Serot
2001-03-08 18:53 ` Ravi Chamarty
2001-03-08 15:26 ` John Max Skaller
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=Pine.LNX.4.10.10103071749420.9499-100000@elroy.ittc.ukans.edu \
--to=ravi@ittc.ukans.edu \
--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).