🚀 go-pugleaf

Thanks, Ralph, for both Documenting Frameworks using Patterns and
Reusing Object-oriented Designs.  I'm not all the way through the
2nd one yet, but I like what I see so far.

In article <Bwx0MG.AHv@cs.uiuc.edu>, 
johnson@cs.uiuc.edu (Ralph Johnson) writes:

|> ... Everybody wants some simple metric by which they can
|> tell whether software is good, but no such metric exists.  ... 

Ok.  What about a "not simple" metric?  Or just thoughts and discussion
on the topic?  

All the papers I have seen on the topic so far say reuse is an 
extension of good software engineering and go on to
talk about those (principles: modifiability; efficiency; reliability; & understandability.  techniques: abstraction & information hiding; 
modularity & localization; uniformity, completeness & confirmability.  
if you like Booch's formulation, anyway).  That looks to me like a good
place to start, but can't we at least talk about things more reuse
specific?  At least sling around some opinions.  I, at least, could
learn something just from hearing what other people think is important
(and not).


-- 
	   _   _
    /_    / ) / ) Jeff Hull           jhull@thor.den.mmc.com
   //_) -/- -/-   1544 S. Vaughn Cir  
/_/ \_/ /   /	  Aurora, CO 80012    303-977-1061

No matter where you go ... there you are.
#include <standard.disclaimer.h>