bouchet vincent:
Hi all,
I think to a "synchronisation" problem : I remember similar problemwith c++ (in an other life) : The value is read before she was write.(with a Transcript, or a debug screen, the execution speed is slower.)
Interesting, now i have at least 2 solutions, Transcript in loops or steal a 486DX at the museum. I thought there were a single thread of execution and have not the necessary background to understand what you say, but i will transmit the suggestion to Ian. Thank you
Nicolas
________________________________________________________________________ iFRANCE, exprimez-vous ! http://web.ifrance.com
On Thu, Jun 29, 2006 at 05:52:25PM +0200, ncellier@ifrance.com wrote:
bouchet vincent:
Hi all,
I think to a "synchronisation" problem : I remember similar problemwith c++ (in an other life) : The value is read before she was write.(with a Transcript, or a debug screen, the execution speed is slower.)
Interesting, now i have at least 2 solutions, Transcript in loops or steal a 486DX at the museum. I thought there were a single thread of execution and have not the necessary background to understand what you say, but i will transmit the suggestion to Ian.
Nicolas,
This is probably not related to your problem, but I will mention it just in case. The Transcript is a very unreliable way to debug something that may be related to timing, because it must be updated in the Squeak user interface process. Instead of the Transcript, it may be better to write to console standard output. If you have OSProcess loaded in your image, you can use OSProcess class>>debugMessage: and OSProcess class>>trace: to write to the console output immediately from the active Squeak process.
Again, I do *not* think that this is directly related to the problem you are trying to solve, but maybe it will help make your debugging more predictable.
Dave
squeak-dev@lists.squeakfoundation.org