Incomplete library class smell
From CSSEMediaWiki
(Difference between revisions)
m (→See also) |
|||
Line 1: | Line 1: | ||
+ | ---- | ||
+ | <div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;"> | ||
+ | ---- | ||
+ | =[http://ybyfonojot.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]= | ||
+ | ---- | ||
+ | =[http://ybyfonojot.co.cc CLICK HERE]= | ||
+ | ---- | ||
+ | </div> | ||
Software reuse is a real buzzword in the object oriented community. Library classes (for example Java's library) are very important when developing a program and because it is often not possible for developers to change the library classes they are using particular effort has to be put into the development of library classes to ensure that they are complete in terms of the behavior they offer. However, this can be difficult and requires thinking of all possible future uses for code, which conflicts with [[You ain't gonna need it]]. | Software reuse is a real buzzword in the object oriented community. Library classes (for example Java's library) are very important when developing a program and because it is often not possible for developers to change the library classes they are using particular effort has to be put into the development of library classes to ensure that they are complete in terms of the behavior they offer. However, this can be difficult and requires thinking of all possible future uses for code, which conflicts with [[You ain't gonna need it]]. | ||
Revision as of 07:12, 24 November 2010
Software reuse is a real buzzword in the object oriented community. Library classes (for example Java's library) are very important when developing a program and because it is often not possible for developers to change the library classes they are using particular effort has to be put into the development of library classes to ensure that they are complete in terms of the behavior they offer. However, this can be difficult and requires thinking of all possible future uses for code, which conflicts with You ain't gonna need it.
See also