Re: [Caml-list] RFH: can't figure out why my QT5 widget bindings segfault

[Goswin von Brederlow <goswin-v-b@web.de>]

On Wed, Apr 06, 2016 at 11:56:21PM +0100, SP wrote:
> On Sat, Apr 02, 2016 at 01:38:41PM +0200, Goswin von Brederlow wrote:
> >With objects each class inherits all the data of the parent while
> >alowing the child to be used with methods of the parent.
> 
> This is part of the problem I'm referring to when I say "tracking the
> changes in the API".
> 
> >You can't do that with records or tuples. And if I have one class
> >definition per Qt5 class anyway I might as well expose that to the
> >user instead of hiding it in modules.
> 
> Yes, it would have to be new approach all together.

Then I'm afraid you have to rewrite Qt. You have to overload every
single Qt class to use the many virtual functions.
 
> There is still merit in having a one-to-one ocaml wrapper for Qt. If
> you can do the wrapping using some generator operating on the headers,
> even better.
> 
> But I would encourage that a higher level, functional wrapper is used
> for applications. It would be a shame if heavy object orientation
> affected user interface codebases because of such necessity.
> 
> -- 
>    SP

Feel free to do that. Personally I think a GUI is the worst fit for
functional programming and the best fit for object oriented. A GUI
screams side effect and mutability to me and a purely functional
approach I think is entirely pointless beyond the academical.

Luckily ocaml allows one to use both functional and object oriented
programming where it fits best.

MfG
	Goswin