rsnd

You should not apologize. As you both asked questions in the lines of "why does it matter," I thaught I did not make myself clear enough. I should apologize for asing something stupid in the first place. You guys did make me realize at some point that my judgement was wrong and thanks to that, I have more choices. Its almost like last year, when I did my first challenge. I probably had one of the best algorithems. Even my professor said so. But everyone was doing it in java and I could not see a simple thing like array buffering instead of creating arrays on every cycle of the loop and discarding them. My algorithem took 16.753 seconds to complete while some managed to produce almost "instant" (<1s) results with algorithems our professor said "would have been 50 times faster if they did it differently." So I have this strange idea that "fast" algorithem wont cut the tree. Also require something vary sharp. Perhaps I am wrong. Someday, I think I will grow up.

__________________
Spread your wings and fly! Chicken!

DaWei

Sometimes you require performance and sometimes you want to achieve it as a matter of the 'best' way to write the program. Unfortunately, most people have no idea how to go about it in a way that yields truly useful results. Here is a link to some material produced by a friend of mine. I wouldn't call it definitive, but it raises very valid points. The guy is not a programmer; he's a biochemist that programs.

__________________
Abstraction doesn't make it impossible to write bad code; it makes it possible to write superior code.
Contributor's Corner: Grumpy on C++ Exceptions DaWei on Pointers