Re: multiple inheritance in Java
On 7/2/2013 2:29 PM, Jeff Higgins wrote:
On 07/02/2013 01:40 PM, Eric Sosman wrote:
On 7/2/2013 1:17 PM, Jeff Higgins wrote:
On 07/02/2013 12:09 AM, Eric Sosman wrote:
Okay. It might have been clearer if you'd chosen names that
weren't already taken -- although, one must admit, that's not easy
to do with Java's ever-growing namespace bloat. (Factoid: The HTML
*index* for the 7.0 API occupies eighteen meg!)
Java never throws anything away. I wonder about a compatibility layer.
rt.jar would contain all of the current stuff, rtc.jar the old.
Not sure what the separation would accomplish. All the
package names would remain unchanged, all the class and method
and field names would remain unchanged, the JavaDoc would still
have to describe them all, and the JVM would need to open one
more file than it already does.
If someone wanted to expend the effort to do the pruning
the following would compile with the compatibility switch on
otherwise throw ClassNotFoundException.
Vector<String> v;
JList<String> l = new JList<String>(v);
I could download JDK9 or JDK9C, I guess only JDK9C compiler
would include the -compatibility switch.
Oh, now I get it. I hadn't realized that you meant the
"compatibility layer" to be unavailable unless specifically
requested. But I think that's a non-starter: Look at all the
"current" classes that still use "old" stuff. Vector, to take
your example, is required by the Swing classes ButtonGroup,
DefaultComboBoxModel, JComboBox, JList, JTable, and JTree,
and perhaps others. (Wisecracks about moving all of Swing to
"old" will be punished with great severity. :)
--
Eric Sosman
esosman@comcast-dot-net.invalid