Perhaps just making Cloneable and Serializable annotations, while deprecating the interfaces?
Although the interfaces will probably not be removed before 1.8 or (dare I say it) 2.0, it would at least encourage using annotations the way they are meant to be used, and interfaces as, well, interfaces! Sent from my iPhone On Mar 4, 2009, at 3:12 AM, Joshua Marinacci <jos...@gmail.com> wrote: > > On Mar 3, 2009, at 10:48 PM, Mark Derricutt wrote: > >> >> Hey all, >> >> Project Coin is all about small language changes for Java 7, whats >> the >> changes of getting a project setup for "small interface/object >> changes" (although these could be breaking..) to fix some >> reallllllllllly annoying marker interfaces, i.e.: > > You are unlikely to ever get a breaking change into core java. On the > other hand, having modules in the language and JRE opens up some new > possibilities. > > >> >> >> * Add clone() to the Cloneable interface, and make Object's >> implementation abstract (or remove it compleately!) - make all >> classes >> in the JDK that implement clone(), implement Clonable (if they don't >> already) >> >> Is this a crazy idea (quite likely its absurd, but so is Cloneable >> NOT >> having clone() as a method. Any other stupid things like that could >> be cleaned up (even if they might break a few things along the way?) >> >> ...and then Buffy staked Edward. The End. >> >>> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javaposse@googlegroups.com To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
