On Nov 7, 2004, at 2:37 PM, Alfonso Guerra wrote:
>> *can* break the code. It *can* fix the code. It doesn't just
>> "reflect
>> the net result of the code on that single variable," it reflects the
>> net result of the code *plus* the code to print the value. And that
>> can be enough to perturb the results.
>
> It doesn't affect the code. It may affect the results, but you won't
> find the source magically corrected by printing variables in the
> debugger.
Sure you can! Please read carefully what Chris was telling you! Just
few weeks ago I had a case where print statement was enough to slow
down one thread and give the app chance to make a right thread
synchronization. Without it the app was crashing... It turned out
someone forgot to put a memory lock....
-- georg --
"War is God's way of teaching Americans about geography."
Ambrose Bierce, writer (1842-1914)
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/extremeprogramming/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
