MethodOverriding

From APIDesign

(Difference between revisions)
Jump to: navigation, search
Current revision (12:17, 19 March 2025) (edit) (undo)
 
Line 5: Line 5:
* ''Java Method Overriding Is FUBAR'' [https://web.archive.org/web/20151001220827/http://weblog.ikvm.net/2011/11/04/JavaMethodOverridingIsFUBARPart3Of.aspx Part 3] ''' of ∞'''
* ''Java Method Overriding Is FUBAR'' [https://web.archive.org/web/20151001220827/http://weblog.ikvm.net/2011/11/04/JavaMethodOverridingIsFUBARPart3Of.aspx Part 3] ''' of ∞'''
* ''Java Method Overriding Is FUBAR'' [https://web.archive.org/web/20151002024459/http://weblog.ikvm.net/2011/11/04/JavaMethodOverridingIsFUBARPart4Of.aspx Part 4] ''' of ∞'''
* ''Java Method Overriding Is FUBAR'' [https://web.archive.org/web/20151002024459/http://weblog.ikvm.net/2011/11/04/JavaMethodOverridingIsFUBARPart4Of.aspx Part 4] ''' of ∞'''
-
* ''Java Method Overriding Is FUBAR'' [https://web.archive.org/web/20151001210629/http://weblog.ikvm.net/CommentView.aspx?guid=f58b4ef6-4077-4f23-a840-b784d28db586 Part 5] ''' of ∞'''
+
* ''Java Method Overriding Is FUBAR'' [https://web.archive.org/web/20151001224815/http://weblog.ikvm.net/2011/11/04/JavaMethodOverridingIsFUBARPart5Of.aspx Part 5] ''' of ∞'''
* ''Java Method Overriding Is FUBAR'' [https://web.archive.org/web/20151002025710/http://weblog.ikvm.net/2011/11/07/JavaMethodOverridingIsFUBARPart6Of.aspx Part 6 ] ''' of ∞'''
* ''Java Method Overriding Is FUBAR'' [https://web.archive.org/web/20151002025710/http://weblog.ikvm.net/2011/11/07/JavaMethodOverridingIsFUBARPart6Of.aspx Part 6 ] ''' of ∞'''
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]].

Current revision

There was a fantastic set of blog posts on Java MethodOverriding by Jeroen Frijters. His blog is long time gone, and googling yields no good results. However I managed to dig the pointers out at

  • Java Method Overriding Is FUBAR Part 1 of ∞
  • Java Method Overriding Is FUBAR Part 2 of ∞
  • Java Method Overriding Is FUBAR Part 3 of ∞
  • Java Method Overriding Is FUBAR Part 4 of ∞
  • Java Method Overriding Is FUBAR Part 5 of ∞
  • Java Method Overriding Is FUBAR Part 6 of ∞

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.

Retrieved from "http://wiki.apidesign.org/wiki/MethodOverriding"
buy