what is the point of developing different classes ?

the monolithic - everything in one place - application is a nightmare to maintain, basically. imagine having to work out and trace a million lines of code, where they all lead and what they do, all in one source file. a nightmare. modularising software allows us to work on small pieces of the problem at once, and, done properly, to change individual modules without affecting others. it's not limited to software, either. look inside your PC. there isn't just one single chip that processes instructions, accesses memory, accesses drives, manipulates the screen, outputs sound and communicates over the network. there are modules that specialize in one of those things. imagine if everything was done by one chip, and then the manufacturer realises they made a mistake in the memory part of the chip. you'd have to replace the whole thing. now imagine a piece of unmodular software, and there's a bug in one small place. you now have to replace the entire thing

it might not seem so at the moment, but when you come to write larger applications, you'll see the benefits of separation

georgemca at 2007-7-8 23:42:59 >