Defender methods and compatibility
Llewellyn Falco
isidore at setgame.com
Sun Nov 28 16:48:09 PST 2010
sorry, i know this must sound like a newbie question, but I am confused as
to the whole point of the default and defender methods for interfaces.
I've been following the thread for a while now, but still can't seem to get
my head around it.
As far as I can tell, this allows you to have Interfaces that act like
abstract objects.
Which is confusing, why not just have abstract objects?
the 1 possible difference I can see is this would allow for multiple
inheritance.
and that leads to a very odd question of
"why would you want to bring back multiple inheritance?"
is there something I am missing here?
llewellyn
More information about the lambda-dev
mailing list