Re: [Evolution-hackers] Problems with camel

[Jeffrey Stedfast <fejj novell com>]

generally, a big hint is when a camel_<type>_new() function doesn't
exist, it means you have to subclass it.

also, the reason it crashed is because you can't cast an object to a
class. (well, you can, but you won't get a valid class pointer)

Jeff

On Tue, 2005-03-01 at 14:32 +0100, Søren Hansen wrote:
> tir, 01 03 2005 kl. 08:49 +0800, skrev Not Zed:
> > And that means actually subclassing it, you can't just create it and
> > override the virtual methods manually.
> 
> Ok, this might be more of a GObject question, but why? I realize now
> that I'm not *supposed* to instantiate it, but I don't understand that
> it fails.
> How could I have found out myself that CamelSession is an abstract
> class?
>