[Caml-list] c++ class to ocaml class or module?

[Caml-list] c++ class to ocaml class or module?

[Joel Reymont]

Would you suggest wrapping a C++ class in a class in OCaml?

Should I pick another approach, e.g. using a module?

	Thanks, Joel

---
http://wagerlabs.com | @wagerlabs | http://www.linkedin.com/in/joelreymont

RE: [Caml-list] c++ class to ocaml class or module?

[Jacques Garrigue]

From: Joel Reymont <joelr1@gmail.com>

>Would you suggest wrapping a C++ class in a class in OCaml?
>
>Should I pick another approach, e.g. using a module?

In C++ classes act both as object generators and modularity providers.
So you should first determine what is the role of the class you're wrapping.

Note also that since the FFI cannot directly create ocaml objects, you
will first need to wrap methods as external functions anyway.
I would only suggest making the extra effort of combining these
functions into classes if sutyping is actively used.

Jacques Garrigue

Re: [Caml-list] c++ class to ocaml class or module?

[Joel Reymont]

On Dec 28, 2010, at 11:15 PM, Jacques Garrigue wrote:
> I would only suggest making the extra effort of combining these
> functions into classes if sutyping is actively used.

This is a large surface C++ API where I need to subclass to provide callbacks.

For example, the initialization arguments to the "engine" class are grouped into a "parameters" class so I need to create the parameters object in C++ and then individually set the members. 

---
http://wagerlabs.com | @wagerlabs | http://www.linkedin.com/in/joelreymont

Re: [Caml-list] c++ class to ocaml class or module?

[Jacques Garrigue]

On 2010/12/29, at 8:26, Joel Reymont wrote:
>> I would only suggest making the extra effort of combining these
>> functions into classes if sutyping is actively used.
> 
> This is a large surface C++ API where I need to subclass to provide callbacks.
> 
> For example, the initialization arguments to the "engine" class are grouped into a "parameters" class so I need to create the parameters object in C++ and then individually set the members. 

As this doesn't seem to involve subtyping, I would suggest just
putting your parameters into an ocaml record, and have a class on the
C++ side that accesses the fields of such a record.
Keep the FFI as simple as possible.
If you need more structure on the ocaml side, you can always add it later.

Jacques Garrigue