Hello Herman.
11 Apr 97 20:42, Herman Schonfeld wrote to Pierre Phaneuf:
 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.
I think it is a matter of personal preferences, whether you like it or not. 
But
for me it helps me break large projects down to smaller more comprehensible
parts.
As an example, I have lately been working on quite a big project, programming 
a GIS program, for the Danish Institute for Arctic Exploration. The basic 
idea is to read some files containing vector data (coordinates collected with 
a Global Positioning System in an airplane) and some other files containing 
bitmap data (satellite-photos).
The basic idea is, that these files have to be read into the program an 
analysed in respect to each other.
The files are very different in structure (binary vs. text) and drawing 
methods (Bit-Blitting vs. GDI-commands), but they will be used in the same 
way in the same window in the same program.
The way to go, is to look at each file type as an object, and then design the 
objects with a common interface. Each filetype object is responsible for 
doing its own reading of files, drawing on the screen and doing it's own 
cleanup.
I can desing a object for each filetype and test it in its own test 
application, so I wont have to worry about destroying some of the things that 
already work (and saving compiletime, while testing).
The really cool thing, is that the next time I have to make a project of that 
kind, I just enherit a new object from the objects that already work.
Christian
--- GoldED 2.50 UNREG
---------------