devestator
Lifetime Member
- Joined
- Oct 25, 2006
- Messages
- 1,550
- Reaction score
- 15
- Points
- 38
/continue is a performance improvement and works in both /for and /while loops, nested or single.
Also my OCD alarm goes off when I see /next being used as a goto improperly, so that was reason enough to change it. The change is recent and was basically pushed through by eqholic but I agree with it. It will make macros look prettier and the logic easier to follow.
Lol we are coding for aesthetics now?
/next x
/continue
Hmmm you are right, the curves in /continue are much more appealing than the mostly harsh straight lines in /next x. Definitely prettier code that way
Yes, I'm joking, mostly lol. I do disagree with a huge macro breaking change for code aesthetics sake though. As a professional developer myself, when changing old stuff, or even creating new stuff, I strongly believe in backwards compatibility unless there is a significant reason not to in order to make transitions into new features as smooth as possible. But, I also have to worry about how many man hours it's going to take to change affected code and things like that. I suppose in your case you don't really have to worry about how much time it's going to take everyone else to change their macros and such.
If it's a significant performance improvement then ok, that is understandable. I haven't ever looked at how the parser works but I thought it parsed and executed line by line. This change, and it being a performance improvement, seem to imply that it parses the entire loop before it executes the lines in it. Maybe some day I'll be bored and have time to look at the parser code and learn how it actually works lol