On Tue, Apr 12, 2005 at 08:36:34PM -0700, Stewart Stremler wrote: > begin quoting Tracy R Reed as of Wed, Apr 13, 2005 at 10:21:20AM +0700: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Stewart Stremler wrote: > > > * After you've learned problem decomposition, design modularization, > > > lexical scoping, the difference between top-down and bottom-up, and > > > the idea that the computer doesn't guess at what you mean but does > > > only what you say. > > > > Can you explain for us the difference between top-down and bottom-up and > > how it helps one to write good code? > > The difference between top-down and bottom-up is that one of 'em starts > at the top and the other one starts at the bottom. And it helps you > to write good code because if you can't tell your top from your bottom > you're going to produce topsy-turvy code. > > -Stewart "Next!" Stremler
Top down means you analyze the program from it's highest functions/behaviors and deconstruct. Bottom up means you identify the critical low-level functions and write them first, letting the program shape up around them. Either approach done purely and without any admixture of the other leads to disaster. Best to combine them and write out-in, if that makes any sense. -- Lan Barnes [EMAIL PROTECTED] Linux Guy, SCM Specialist 858-354-0616 -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
