Re: Sorry was:I want to understand (and new questions)

[Lars Hallberg <lah micropp se>]

Sorry

I was to tierd yesterday :-( Hope You did ignore this ;-)

> The other way around, use a C library from C++ is also esy so the question
> comes down to void ;-) With one exeption - callbacks and exeptions.

This holds, so Owen is right - We shuld drop this thred.
 
> If the event handler is defined in an library that might be anoying. I
> guess it is anoying for some langage bindings to ;-)

This *is* a slight anoyans :-(
 
> What can be done?
> 
> 1) Only use the low level GTK and write a new C++ framework.
> 
>    * Some stuff like confile interface and thems can hopfully be reused.
> 
>    * I have not looked at the source but i geuss the callbaks is
>      raised from the widgets themself wich means all the widgets
>      will be reimplemented :-(

Well - I should not dwell more over this untill I deeply examen the
source. If I do my glib C++ wrapper right we may have a tool for
solving this (provided that GTK keep track of handlers with help of
glib. All details saved for later...

> 2) Introduse an #ifdef branch that C++:ifies the GTK framework part
> 
>    * Advantage over abowe is that most parts of the widgets will
>      be reused an that the two interfaces will follow eachother
>      more naturly i the development.
> 
>    * Will slightly inkrease GTK owerall source complexity.
> 
>    * This will be a HUGE job but can be joint efort from GTK--,
>      VDK and other C++ users. Thanks to CVS the efort shuld not
>      need to come in the way for C developer (not much at least)

I dont't want this. This means You ned two GTK-lib on the mashine - One
compiled for C and one for C++. I do not want this at all, sorry...
 
> 3) Live with an restricted usage of exeptions forewer :-(

We have to do this for a while ;-)

Sorry for the line noice /Lars