On Wed, Nov 05, 2008 at 08:12:40PM EST, Tim Rowe wrote: > 2008/11/6 Chris Jones <[EMAIL PROTECTED]>: > > > Begs the question .. how do I tell what is an object-oriented vs. a > > procedural problem? > > Practice, largely, so you're doing the right thing (provided you don't > trust your /real/ backup data to a tutorial program). If you find that > the program is at its neatest when it's just a couple of methods in > one class, it was a procedural problem.
but you do have to go through the motions .. to "find" it .. > Actually, from your description of the problem -- that the interest is > in all the "what if" cases -- suggests that it's a specification > problem rather than a design or implementation problem, so rather than > recoding it it might be worth looking at various approaches to > requirements capture and specification. I'm one of them that need to get their hands dirty a bith .. lack the power of abstraction. Need to do some building before I can specify. -- http://mail.python.org/mailman/listinfo/python-list
