BLM> The best source of useful information to me so far is this 
 BLM> echo, followed closely by Glen McCluskey's "C++ Newsletter". 
 
 CAM> Well, I have a very comprehensive set of lecture notes, brilliantly 
 CAM> typed out in Low-ASCII and I'm going to make them available for 
 CAM> FREQing.  They combine a little OOAD theory with C++ and are just 
 CAM> the thing for the beginner. 
 
 Please notify ALL when you make that available for FREQ, I'll have 
 to ask my sysop if he would be so kind.  thanx 
 
 By the way, I think it was you that recommended the book "Object- 
 Oriented Analysis and Design with Applications" by Grady Booch.  I 
 just picked it up today, and it seems well worth the $60.00 I paid 
 for it.  thanx 
 
 BLM> I have never seen a clear definition of object oriented 
 BLM> programming. 
 
 CAM> Somebody in this echo posted a brilliant description of 
 CAM> exactly what OOD is....see the end of this message. 
 
 Any little bit of information helps greatly, thanks again. 
 
 CAM> Let me give you an example.  Let's say we wanted to model 
 CAM> everything in a horse racing. 
 
 BLM> That's all well and good if you want to race horses, but what 
 BLM> if you wanted to extract functions from a C program. 
 
 CAM> "Normally", you would start with a spec, and isolate the 
 CAM> components.  What you are talking about is taking existing C 
 CAM> code and Seeplusplusifying it.  :) 
 
 
 Actually, No.  What I want is a small utility that will do for C 
 modules what PKUNZIP does for ZIP archives.  Take all the procedures 
 (files) within the module (archive) and send them as output to their 
 own file.  Why?  I really have no use for such a utility, but it's 
 the first thing that came to mind and should be a pretty simple program. 
 
 CAM> Well, I can give you a simple example of that too. 
 
 Thanks anyway, but most of that was over my head so I'll ignore it 
 for now.  Maybe come back to it later when I have a greater understanding 
 of C++ and object oriented design. 
 
 Now, according to your advice above ("start with a spec, and isolate the 
 components") to get my program off the ground I should do this... 
 
 System Specifications: 
 
     1. Take input from C module files. 
     2. Output to individual files all procedures found on 
        input. 
 
 Now that I have my system's specs I should NOT do this... 
     1.  Create input function 
     2.  Create search function 
     3.  Create output function 
 
 But I SHOULD do this... 
     1.  Create InputFile object of 
          // the InputFile object knows that it is a C module 
     2.  Create OutputFile object 
          // the OutputFile object knows that it is a C procedure 
 
 Is that all correct?  Once again thank you for all your help. 
 
 What I think I have learned so far... 
     1.  A program can be written in C++ without using object oriented 
         design. 
     2.  A program can be written using object oriented design without 
         using an object oriented language. 
     3.  Numbered lists really look cool. 
     4.  Object oriented design is concerned with the actual physical 
         objects that a program interacts with.  I.E. disk files, the 
         screen, the keyboard, etc... 
 
  
 
*Welfare and TV are today's bread and circuses. 
  
blm
--- FLAME v1.1
---------------