MethodOverriding
From APIDesign
(Difference between revisions)
(New page: There was a fantastic set of blog posts on Java MethodOverriding by Jeroen Frijters. His blog is long time gone, but I managed to dig the pointer out at https://web.archive.or...) |
|||
| Line 4: | Line 4: | ||
What can one say? In general: [[OOP]] sucks! When you have to live with it read [[ClarityOfAccessModifiers]] and ''never expose non-API'' superclasses and other elements in your [[API]]. | What can one say? In general: [[OOP]] sucks! When you have to live with it read [[ClarityOfAccessModifiers]] and ''never expose non-API'' superclasses and other elements in your [[API]]. | ||
| + | |||
| + | * [https://web.archive.org/web/20151001210629/http://weblog.ikvm.net/CommentView.aspx?guid=f58b4ef6-4077-4f23-a840-b784d28db586 Part 5] | ||
| + | * [https://web.archive.org/web/20151002025710/http://weblog.ikvm.net/2011/11/07/JavaMethodOverridingIsFUBARPart6Of.aspx Part 6 ] | ||
Revision as of 12:08, 19 March 2025
There was a fantastic set of blog posts on Java MethodOverriding by Jeroen Frijters. His blog is long time gone, but I managed to dig the pointer out at
What can one say? In general: OOP sucks! When you have to live with it read ClarityOfAccessModifiers and never expose non-API superclasses and other elements in your API.
Follow
