On 1-May-07, at 10:36 AM, Rubber Chicken Software Co. wrote: > At 11:04 AM 5/1/2007, you wrote: > >>>> This whole discussion misses the point. Maintenance of the code >>>> "trumps" all the merits of putting DIM statements in any >>>> other place but the top of the method since putting DIM statements >>>> within the code are negligible at best. If you scatter your DIM > >>> That is absolutely and patently incorrect for proper maintenance of >>> code -- putting the declarations of variables as close as >>> possible to >>> their use is one of the basic tenets of good software design. > >> This starts to border on religion. >> How the heck did people write good software in C, Pascal or RB when >> this capability was not available ? >> Careful coding. > >>> Here's the kicker: If you have your declarations of variables in >>> the >>> immediate vicinity of their use, you have now made it possible to >>> easily refactor that code simply by moving that entire block to a >>> new >>> location. > > Good discussion. I've gone back and forth about this, read lots of > things about it.
There are lots of things to consider when you discuss "universal truths". James Shore, recipient of 2005 Gordon Pask Award for Contributions to Agile Practice, has an excellent article on this <http://www.jamesshore.com/Articles/Quality-With-a-Name.html> What I, and any team I work with, consider good design varies from another teams assessment. Capabilities, tools, backgrounds and a lot of other factors affect what is considered good design by any team. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
