|Sent on:||Tuesday, August 14, 2012 1:55 PM|
On Wed,[masked] at 13:34 -0400, Richard Warburton wrote: […] > tl;dr - if you add a method like 'filter' to an interface like > Collection then you're making a binary incompatible change to the API. > So you provide a default method that is inherited if no alternative > is provided in order to be able to more easily evolve interface based > APIs. OK, so this is just backward compatibility hacking. This is how cruft evolves :-( > > Is there a document explaining all this you can point me at? > > http://cr.openjdk... Aha, mixins, traits. Now I can support the feature even though it isn't really mixins or traits. I suspect if the marketing of the feature had been "moving towards mixins and traits in Java" rather than "we need this feature to hack round problems with introducing lambda functions", then there would have been more excitement and less scepticism. -- Russel. ============================================================================= Dr Russel Winder t: [masked] voip: sip:[address removed] 41 Buckmaster Road m: [masked] xmpp: [address removed] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
This email message originally included an attachment.