Re: Is 'Final' for classes and methods a good feature or something that should be eliminated?
- From: Michael Feathers <mfeathers@xxxxxxxxxxxxxxxx>
- Date: Mon, 26 Feb 2007 06:44:25 GMT
rmoldskr+usenet@xxxxxxxxx wrote:
Michael Feathers <mfeathers@xxxxxxxxxxxxxxxx> wrote:
It's not just a simple matter of being annoying. Final can make code untestable.
It hampers _one_ particular testing technique, it doesn't make anything
untestable.
Which one technique are you thinking of?
----
Michael Feathers
http://www.objectmentor.com
http://michaelfeathers.typepad.com
author of: Working Effectively with Legacy Code (Prentice Hall 2005)
.
- Follow-Ups:
- References:
- Is 'Final' for classes and methods a good feature or something that should be eliminated?
- From: Michael Feathers
- Re: Is 'Final' for classes and methods a good feature or something that should be eliminated?
- From: rmoldskr+usenet
- Re: Is 'Final' for classes and methods a good feature or something that should be eliminated?
- From: Michael Feathers
- Re: Is 'Final' for classes and methods a good feature or something that should be eliminated?
- From: rmoldskr+usenet
- Is 'Final' for classes and methods a good feature or something that should be eliminated?
- Prev by Date: Re: Relational-to-OOP Tax
- Next by Date: Re: It's the Psychology, Stupid (Was: The reality of Topmind)
- Previous by thread: Re: Is 'Final' for classes and methods a good feature or something that should be eliminated?
- Next by thread: Re: Is 'Final' for classes and methods a good feature or something that should be eliminated?
- Index(es):
