Re: Is 'Final' for classes and methods a good feature or something that should be eliminated?
- From: rmoldskr+usenet@xxxxxxxxx
- Date: Sun, 25 Feb 2007 23:33:25 -0600
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.
--
Leif Roar Moldskred
.
- 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
- 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: Relational-to-OOP Tax
- 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):
