On Fri, 2006-08-11 at 15:36 +1000, Jonathan Morgan wrote: > > object indicates a GObject subclass. They can have fields, methods, > > constructors, virtual_methods, properties, and signals. > > Not all objects seem to have parents (see, for example, GtkStock).
The C source parser is not 100% bug free. ;-) > > struct and boxed are non-GObject structs where boxed also has a GType. > > They only have fields, methods, and ctors. > > Thanks for that - that's pretty well what I wanted to know. The tags > are generally pretty easy to guess what they mean, though not always > all the fine details. > > Sorry about type - I really meant class. How does class differ from object? Class is basically an aggregator for instance-less methods. When generated, they produce classes with all static methods. For example, if there is a series of foo_bar_* functions in the parse, and they don't have a FooBar* first parameter, they produce a class element to aggregate the methods into a single type. Since every method must be associated with a type, this aggregated solution keeps us from having one monster class with every unclaimed method in the library. > I'm presuming that interface is something like an object without > fields. Is that correct? Class should have only shared/static methods. Now I'm really wondering what you are up to that you would be asking these questions. ;-) -- Mike Kestner <[EMAIL PROTECTED]> SUSE® Linux Enterprise 10 Your Linux is ready™ www.novell.com/linux _______________________________________________ Gtk-sharp-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/gtk-sharp-list
