For GTK+ the problem is constrained - not surprisingly - because the
library was designed to make it easy to write bindings for: the library
is written in C and all the OO machinery is provided in the library.
So, given an OO library, one approach might be to introduce top-level
wrapper functions for a class's constructors and methods, and top-level
accessor functions for a class's members and export those top-level
functions. Then you could create bindings like mGTK does. Hopefully.
Or perhaps you were asking about OO representation on the ML side of the
binding?
Phil
On 16/02/2017 11:49, Gergely Buday wrote:
Hi,
there are known theoretical difficulties bridging SML code to object
oriented interfaces.
What can be done practically?
mGTK has a description here
https://www.usenix.org/legacy/event/usenix04/tech/freenix/full_papers/larsen
/larsen.pdf
Is there any other way?
- Gergely
_______________________________________________
polyml mailing list
[email protected]
http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
_______________________________________________
polyml mailing list
[email protected]
http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
