>Ok, I think I understand. The easiest way to reuse code is CopyPasteReuse; the easiest way to reuse and maintain that code may be to use CodeReuse or even InheritanceReuse?

Well, more to the point, there are several types of reuse. Code Reuse initially appears noble, but it's really at the wrong level of abstraction for OO. Reuse in OO is all about reusing systems of objects. Anything less is to underachieve in a big way.

Note that it's possible to reuse systems of objects whom themselved don't reuse much code. It's as much about abstracting roles and responsibilites as it is about the code. Code is, after all, just an implementation detail.

>Btw, anything you can throw in about ComponentReuse? Its blank.

The problem with defining Component Reuse is there are still myriad definitons for the term "Component" and moreover components have a wide range of granularity, from widget to framework, so it's not easy to nail that one down.