HS> I fail to see the big hype about OOP & OOD.
 HS> Please explain where it can be used and how this will make it better.
 HS> I am thouroughly familiar with OOP & OOD so there's no need for a
 HS> definition.
For example, in this OO database I made (a casket inventory management 
program, where a casket is made of a case, handles/ornaments, an interior, 
plus some options (lighting, sealing, etc...)), there's a TItem class and a 
TModel class, which is a descendant of TItem. I have this single database of 
TItem, that (through polymorphism) can contain both TItem objects and TModel 
objects. So you can sell both a complete casket (a TModel object) or a single 
replacement handle for a broken one (a TItem object). In *both* cases, those 
use the same code.
This is a simple example, but for me, the biggest time saver is the sharing 
of code for multiple cases in a single program, next comes code reuse between 
many programs (like my filter classes, to encrypt/decrypt, 
compress/decompress, all on the fly, through a stream.
Pierre
... Two most common elements in the universe: Hydrogen & Stupidity.
--- FMail/Win32 1.20
---------------