Re: Repeat ... kind'a

re: you might consider using the more ubiquitous /* ... */ Yes, I have done that. However, I have been "conditioned" to distrust that format. I use the "ubiquitous" format extensively for commenting blocks of code. ie: How did we get here, what are we doing here, and what do we expect as a re

Re: Repeat ... kind'a

It seems to me this is a bug that should have been caught during the script compilation phase, instead of during execution. somehow indicating a runtime error on the prior statement. It cost me several hours and some lost data to figure it out, primarily because of the rare circumstances that ca

Re: Repeat ... kind'a

As an alternative, you might consider using the more ubiquitous /* ... */ form to comment out large blocks of code. The biggest benefit is no extra characters in front of each line, but you do need to add the (4) characters manually. Regards, Scott Rossi Creative Director Tactile Media UX/UI

Re: Repeat ... kind'a

Craig Newman: re: I would cringe if I saw someone using a reserved word as a variable, and blanch if that word was as deep and embedded as "true". You are lucky the machine did not explode. What the heck are you talking about? It was a TEST script created to show the glitch. My real script loo

Re: Repeat ... kind'a

I ran into a similar situation once with a leftover "break" command when converting a switch statement to a series of if statements. Might be worth including that in the QCC report Pete lcSQL Software Home of lcStackBrowser and SQL

Re: Repeat ... kind'a

Terry Dennis wrote: > Much fiddling later, I discovered the issue. It was a runtime > “oops”. > Check out the following code snippet, which shows the execution > error. I threw it into button “Capture”s script: > > on testOOPS >put 1 into t1 -- Superfluous for testing purposes >put 2 i

Re: Repeat ... kind'a

since exit repeat can technically be a "stand alone" type of statement, it indeed might only be caught on execution. I'm with you though, it would be better if the engine looked to make sure it was actually inside a repeat loop. Having said that, if you do a function call that checks things, I th

Re: Repeat ... kind'a

I would cringe if I saw someone using a reserved word as a variable, and blanch if that word was as deep and embedded as "true". You are lucky the machine did not explode. Try this: on mouseUp --put "66" into true -- uncomment, and you will get a compile-time error, never mind run-time