Gee RFC: Moving sane default implementations without any overhead to interfaces



As there is support for virtual functions in interfaces I'd like to get
comments regarding moving some implementation from abstract classes to
interfaces.

The methods proposed to change:
 - Should have implementation based on different methods
 - Do not introduce any additional fields etc.

Some classes (AbstractMultiSet) will stay largely intact.


Pros:
 - Allowing to reuse of implementations that cannot inherit from
abstract classes.
 - More GObject-likeness IMHO (and partially C#-likeness)

Cons:
 - Yet another breakage of API/ABI in 0.7
 - Some people don't like virtual methods in interfaces
 - Less Java-likeness

Regards

Attachment: signature.asc
Description: This is a digitally signed message part



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]