Parallax has two BASIC Stamp Editors available, Version 1.33 for BASIC Stamp 2 and Version 2.0 Beta 1. Which one is your team using?
i made a colorized IDE for us to use…
i’m hopefully going to release it soon. 
*jeremy
Last year’s editor was good enough, and so we are using it again this year
We are now using the PBASIC 2.5 Editor v2.0 Beta. No problems so far…
PBASIC 2.5 just for the fact it has real if…then…else statements and do…loops. No more gotos in our robot code.
If you’re still using PBASIC 2.0 format in the v1.33 editor, I suggest you at least look at the differences between the default codes in each.
I find the PBASIC 2.5 far more intuative without its need for gotos to supply any kind of looping structure.
I’ve been working with the Innovation FIRST control system since the beginning and PBASIC 2.5 is the biggest ‘improvement’ made to it.
*Originally posted by Adam Krajewski *
**PBASIC 2.5 just for the fact it has real if…then…else statements and do…loops. No more gotos in our robot code.If you’re still using PBASIC 2.0 format in the v1.33 editor, I suggest you at least look at the differences between the default codes in each.
I find the PBASIC 2.5 far more intuative without its need for gotos to supply any kind of looping structure.
I’ve been working with the Innovation FIRST control system since the beginning and PBASIC 2.5 is the biggest ‘improvement’ made to it. **
Goto’s are a little confusing, but the if/then, select/case/end selects are more confusing. If they made the language like VB, than it would be better.
*Originally posted by Raven_Writer *
**Goto’s are a little confusing, but the if/then, select/case/end selects are more confusing. If they made the language like VB, than it would be better. **
cringes
VB?
When I see VB in embedded systems, I’m becoming a material scientist instead of an electrical engineer. 
I’ll stick with a tried and true if…then…else and select…case iterative language for FIRST robot programming.
Gotos aren’t the problem, it’s how people use gotos. In the case of PBASIC 2, it’s all you had to create looping structures. On the other hand, you could also weave your code into a indecipherable mound with intertwining gotos.
The if…then…goto structure was completely reverse logic to me. “If true, skip to the goto” made no sense to me because I wrote it like a standard if…then statement only using the opposite logic. Very confusing. I much prefer the standard if…then…else structure of PBASIC 2.5.
For more advanced designs, java may be the answer. 2.5 still gives me a leap in faith of PBASIC, though.
Adam
I’m using 2.5, since I prefer not to litter my code with gotos. When I learned BASIC, my teacher’s rule was to never, ever use goto statmements. Every time I use one in PBASIC 2.0, I think about that. 2.5 just has better syntax without all those gotos.
2.5 all the way
if then else is the way to do it …
i was looking at another teams auton code in 2.0 it was an ugly mess
2.5 makes it so much easyier