[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gtkmm
Subject:    Re: [gtkmm] Wrapping GError args as exceptions?
From:       Karl Nelson <kenelson () ece ! ucdavis ! edu>
Date:       2002-01-28 16:53:36
[Download RAW message or body]

> On Fri, 2002-01-25 at 08:01, Murray Cumming wrote:
> 
> > > > I don't like the idea of saying 'Use try/catch here if you expect it to
> > > > work, but don't actually expect it to work all the time'.
> > > 
> > > It is just that all on_ should really be 
> > > 
> > >   virtual on_pressed() throw();
> > > 
> > > (throw() here means that function must no throw and must catch 
> > > anything it gets from what it calls.  Unfortunately, use of throw()
> > > is not well supported.)
> > 
> > Is it possible for libsigc++ to enforce this? - I mean, to not allow any
> > method to be a SigC::Slot if it isn't marked throw(), if the compiler
> > supports it.
> > 
> 
> Do you really want to enforce this?  It seems to me you only want the
> nothrow business because of the Gtk link, while many people may use
> libsigc++ in pure c++ context, and hence would want/need to throw
> through the signal.

If we could enforce it we would do so only on the Gtk related 
functions.  Sigc++ will accept throws and I don't intend to change that.
We should have some makings for expection handling in gtkmm right
now, but it is still debatable as to how useful it is.

--Karl

_______________________________________________
to unsubscribe or change your subscription parameters :
https://lists.sourceforge.net/lists/listinfo/gtkmm-main
[prev in list] [next in list] [prev in thread] [next in thread]