>Arnon, hopefully, i will get this posted by
>adding up front!
>i understand that tools are improving, but
>according to article
>in WINDOW TECH magazine March 96; oop is only
>acheiving a 10-15%
>reusability;

i don't care how it works for other ppl - i only care about
what it does to my productivity - and anyway IMHO when u create
classes with reusibility in mind (e.g. try to generalize a class and use sub-classes for specific proposes etc.)
the reusability rate is much higher
and anyway OO is not just about code reusability e.g.
it is also about encapsulation (generally : every module should hide some concepts from the rest of the system)
dividing the project into small modules reduces the complexity of each object, and to autonomeous modules
- by this for example if u make a change in one module
u don't have to run about all ur app. and make changes there

and btw, these are not new ideas e.g. encapsulatoin has been around since the early 70s



> and ive been doing better than that
>with the
>techniques that have been around since 1962 and
>published by
>the same gurus who are now tauting oop (yourdon
>etc).

if these ppl are indeed gurus - don't u think there might be more than hype behind all thier OO tauting :)

btw one OO concept i am missing in VFP -is multiple inheritance
but ,oh well, i guess u can't have everything

Arnon