Errata 6
From APIDesign
(2 intermediate revisions not shown.) | |||
Line 1: | Line 1: | ||
- | The [[chapter 6]] discusses '''protected abstract''' methods and says that removing such method is source compatible | + | |
+ | ==== [[Errata 6|Page 89]] ==== | ||
+ | |||
+ | The [[chapter 6]] discusses '''protected abstract''' methods and says that removing such method is source compatible. In fact that was true until [[Java]] 5 appeared. However the newly introduced ''@Override'' [[annotation]] changed everything. | ||
<source lang="java" snippet="anagram.ui.Anagrams"/> | <source lang="java" snippet="anagram.ui.Anagrams"/> | ||
Line 12: | Line 15: | ||
-- Rijk van Haaften, Oct 8, 2010 | -- Rijk van Haaften, Oct 8, 2010 | ||
+ | |||
+ | ==== [[Errata 6|Page 90]] ==== | ||
+ | |||
+ | In the example of defining inserting new super class into existing class hierarchy, the whole source code should have been shown. The newly created ''SimpleHelloClass'' should define no argument method. The original ''HelloClass'' shall extend it and keep definition of the more complicated ''sayHelloTo'' method with one string argument: | ||
+ | <source lang="java" snippet="design.insert.superclass1"/> | ||
+ | <source lang="java" snippet="design.insert.superclass2"/> | ||
+ | |||
+ | [[User:Cordeo|Cordeo]] 21:47, 7 October 2010 (UTC) |
Current revision
Page 89
The chapter 6 discusses protected abstract methods and says that removing such method is source compatible. In fact that was true until Java 5 appeared. However the newly introduced @Override annotation changed everything.
Code from Anagrams.java:
See the whole file.public abstract class Anagrams extends javax.swing.JFrame implements UI { protected abstract WordLibrary getWordLibrary(); protected abstract Scrambler getScrambler(); public void display() { initWord(); setVisible(true); } }
If you create a new version of public abstract class Anagrams dropping either getWordLibrary or getScrambler (or both), the @Override annotation in AnagramsWithConstructor will cause the compiler to complain:
Code from AnagramsWithConstructor.java:
See the whole file.public class AnagramsWithConstructor extends Anagrams { private final WordLibrary library; private final Scrambler scrambler; public AnagramsWithConstructor( WordLibrary library, Scrambler scrambler ) { this.library = library; this.scrambler = scrambler; } @Override protected WordLibrary getWordLibrary() { return library; } @Override protected Scrambler getScrambler() { return scrambler; } }
Source compatibility is gone. As an API designer of public class Anagrams you don't know whether your users (writing class AnagramsWithConstructor) will use @Override. As a result don't even try to remove protected abstract methods from an API. It was never good idea anyway and since Java 5 it is not backward compatible.
-- Rijk van Haaften, Oct 8, 2010
Page 90
In the example of defining inserting new super class into existing class hierarchy, the whole source code should have been shown. The newly created SimpleHelloClass should define no argument method. The original HelloClass shall extend it and keep definition of the more complicated sayHelloTo method with one string argument:
Code from SimpleHelloClass.java:
See the whole file.public abstract class SimpleHelloClass { public abstract String sayHello(); }
Code from HelloClass.java:
See the whole file.public abstract class HelloClass extends SimpleHelloClass { public abstract String sayHelloTo(String who); }
Cordeo 21:47, 7 October 2010 (UTC)