Arf Well-Known Member Licensed User Longtime User Mar 26, 2015 #1 a strange error just suddenly started occurring. It seemed to start happening after I switched from debug to signed key. Code: For fvtref = 0 To 999 'some code in here Next Error description: Regular variable followed by '=' expected. Occurred on line: 73 For fvtref = 0 To 999 Word: . any ideas?
a strange error just suddenly started occurring. It seemed to start happening after I switched from debug to signed key. Code: For fvtref = 0 To 999 'some code in here Next Error description: Regular variable followed by '=' expected. Occurred on line: 73 For fvtref = 0 To 999 Word: . any ideas?
thedesolatesoul Expert Licensed User Longtime User Mar 26, 2015 #2 What is fvtref declared as? Upvote 0
Arf Well-Known Member Licensed User Longtime User Mar 26, 2015 #3 Code: Dim fvtref =0 As Int Eveything fine in legacy debug, but not when I use rapid debug - just discovered that. That for loop has been in there for a whole days worth of succesful compilations till now. I've gone back to debug key, problem still there so seems only related to Rapid Debug Upvote 0
Code: Dim fvtref =0 As Int Eveything fine in legacy debug, but not when I use rapid debug - just discovered that. That for loop has been in there for a whole days worth of succesful compilations till now. I've gone back to debug key, problem still there so seems only related to Rapid Debug
RandomCoder Well-Known Member Licensed User Longtime User Mar 26, 2015 #4 You would not normally declare variables this way. Try... Code: Dim fvtref As Int 'or if needing to set initial value (not in process globals) Dim fvtref As Int = 0 Upvote 0
You would not normally declare variables this way. Try... Code: Dim fvtref As Int 'or if needing to set initial value (not in process globals) Dim fvtref As Int = 0
Arf Well-Known Member Licensed User Longtime User Mar 26, 2015 #5 It has made no difference, error is still there :-( Upvote 0
T Troberg Well-Known Member Licensed User Longtime User Mar 27, 2015 #6 Could it be some hard to detect typo? Have you tried just erasing the code and typing it again? Upvote 0
klaus Expert Licensed User Longtime User Mar 27, 2015 #7 Post a small project showing the problem. Upvote 0
Arf Well-Known Member Licensed User Longtime User Mar 27, 2015 #8 Troberg - No typos, it compiles fine in legacy debug, just not rapid debug. I have attached a stripped down project. Thanks guys. Attachments ForLoopProblem.zip ForLoopProblem.zip 428.2 KB · Views: 250 Upvote 0
Troberg - No typos, it compiles fine in legacy debug, just not rapid debug. I have attached a stripped down project. Thanks guys.
klaus Expert Licensed User Longtime User Mar 27, 2015 #9 I get it too. Erel should have a look at it. As a workaround use a local variable in the for / Next loop and set the global variable to local one after the loop if you need it. Upvote 0
I get it too. Erel should have a look at it. As a workaround use a local variable in the for / Next loop and set the global variable to local one after the loop if you need it.
Arf Well-Known Member Licensed User Longtime User Mar 27, 2015 #10 OK will do. Glad it's not me going mad! Thanks Klaus. Upvote 0
Erel B4X founder Staff member Licensed User Longtime User Mar 27, 2015 #11 It is indeed a bug that happens in rapid debug mode, in classes with a global variable as the for iterator. It will be fixed. Upvote 0
It is indeed a bug that happens in rapid debug mode, in classes with a global variable as the for iterator. It will be fixed.
Mashiane Expert Licensed User Longtime User Mar 28, 2015 #12 Thanks Erel, will wait for the update, I almost thought I was also doing something wrong... Upvote 0