Re: Can't abort a loop with Print inside (V6)
- To: mathgroup at smc.vnet.net
- Subject: [mg83157] Re: Can't abort a loop with Print inside (V6)
- From: Bill Rowe <readnewsciv at sbcglobal.net>
- Date: Tue, 13 Nov 2007 03:40:32 -0500 (EST)
On 11/12/07 at 5:09 AM, bhu at cvs.rochester.edu (Bo Hu) wrote: >This is not about a loop running faster than one could stop it >before it ends. The simple loop runs for quite a few seconds on my >Macbook Pro, because of the Print statement. It appears to be >improper synchronization between the kernel and the front end. More >like a misfeature if that's the intended behavior. I did not mean to imply the loop would complete sooner than one could stop it before it ends. Instead, I was trying to describe the case where the time for the to see a key press is to small. That is a sufficiently tight loop simply doesn't allow enough time for the key press to be seen. As far as I know, this has always been present. And I do not believe this issue is strictly a Mathematica issue. Any program that runs a sufficiently tight loop will see the same behavior. I believe the only way Wolfram could prevent this behavior is to intentionally place a maximum loop rate. That is intentionally add a minimum delay into loops so that there is time to see user key presses. And I think this would be more of a problem than the current situation. -- To reply via email subtract one hundred and four