<snip><br>Python is that refactoring is usually really easy.<br></snip><br><br>thats a good thing to know.<br><br>i was originally going to just start out the naive way and refactor as python became more familiar. i think that approach may work best for me - take baby steps and refactor as i my knowledge and experience grows. <br>
<br>thanks again<br>mark<br><br><br><br><br><br><div><span class="gmail_quote">On 12/03/2008, <b class="gmail_sendername">Tim Golden</b> <<a href="mailto:mail@timgolden.me.uk">mail@timgolden.me.uk</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
mark.a.brand wrote:<br> > Hi Tim:<br> ><br> > Thanks, that was what I was after, but maybe you are right a couple of extra<br> > for loops is not looking too bad after all.<br> <br> <br>The code looks a little scary at first sight but it's<br>
not that bad ;)<br> <br> It's one of those things everyone learns to weigh up when<br> they're putting together code / data. How "clever" do I<br> try to be. Sometimes there's clear benefit (or at least<br>
no clear disadvantage). Other times it's the result of<br> overengineering -- and often up front. You may find, for<br> example, that the .executemany in the sqlite example gives<br> a performance benefit over Elixir's more explicit looping,<br>
but you might not (or it might not be significant). Go<br> with what's clearest first, then look for optimisations where<br> you really need them.<br> <br> [One of] The great thing[s] about Python is that refactoring<br>
is usually really easy. The two solutions I outlined did<br> (broadly) the same thing. You could make them even more<br> similar with a little work. Each one is only a couple of<br> dozens of lines of code. If you started with one and decided<br>
later that the other was preferable, it would be really simple<br> to swap one out and the other in. Obviously, it's not always<br> that easy but it's certainly easi*er*.<br> <br> Good luck with the project. Do come back for more help<br>
(or hindrance).<br> <br> TJG<br> <br>_______________________________________________<br> python-win32 mailing list<br> <a href="mailto:python-win32@python.org">python-win32@python.org</a><br> <a href="http://mail.python.org/mailman/listinfo/python-win32">http://mail.python.org/mailman/listinfo/python-win32</a><br>
</blockquote></div><br>