Re: Is 'Final' for classes and methods a good feature or something that should be eliminated?
- From: Thomas Gagne <tgagne@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 26 Feb 2007 13:37:49 -0500
Daniel T. wrote:
<snip>So final isn't the problem, but an imperfect interface is. If
It sounds to me like the blame should be placed on the lack of an
interface for the client to use, not in the fact that this particular
server isn't designed to be sub-classed.
I think, instead of insisting that 'final' is at fault, you should be
insisting that interfaces be more prevalent in the library in question.
interfaces aren't perfect then classes and methods shouldn't be assumed
perfect by declaring them final.
Assuming no interface is perfect and no programmer can predict every
conceivable legitimate use of their code, should anything ever be
declared final?
--
Visit <http://blogs.instreamfinancial.com/anything.php>
to read my rants on technology and the finance industry.
.
- 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: Daniel T.
- 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: Need advice on standarizing documentation in a project
- Index(es):
Relevant Pages
|
