Hi Kevin, my Supervisor isn't really a programmer so he may not even know this, his roots are OO design. Yes I will be using C# (if i have time to learn it, I have heard it is like Java which I already know, if not I was going to do it in VB.Net which I also know, and I found a program that converts from vb to C#) and the .net framework to create my product unless you can suggest an easier method to save on time.
Aaron On 14/04/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > >----- Original Message ----- > >From: "Aaron Jones" <[EMAIL PROTECTED]> > >To: <[email protected]> > >Sent: Friday, April 14, 2006 12:05 PM > >Subject: Re: [sqlite] Structured or Object-Oriented? > > > > >Hi John, I fully understand, and if It wasn't for my final degree I would > >simply just go with the flow, but I have to choose a method and justify > why > >I chose it, which is doing my headin at the moment. lol > > > >Thanks for your comments. > > > >Aaron. > > The arguments for using OOP could be high modularity, encapsulation of > SQLite database functionality, multiple instances and heredity, > association > of data with its related methods, the fact that the language and platform > you are using (C# and DotNet no?) is already strongly OO. > As I understand it, structured programming does not actually exclude OO: > maybe your tutor is putting you under test to make sure you have a good > grasp of the fundamentals; > The nice thing about OOP is that you can make it self commenting: > > If DatabaseIsConnected > then > OpenMainModule > else > TellUserDatabaseIsDown; > CloseProgram; > (Pseudocode) > > The four methods (DatabaseIsConnected, OpenMainModule, > TellUserDatabaseIsDown, CloseProgram) > can then be reduced in their internals to the same type of structure (in > its > way a form of structural or at least procedural programming); > In your situation I would have a real blitz on OOP: it's not just theory, > it > will be extremely useful in the real world (many of the worst problems I > have seen in my recent collaborations would have been avoided with prior > rigorous application of OO from their beginnings: someone with a good > grasp > of OO would simply not create certain structures); > > > >
