Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • sorry, the "argument" I presented in the last paragraph is supposed to be an argument in favour of an exclusive loop, it basically says that there's always a value one greater than the last valid loop index anyone might use "in practice". I'm trying to decide whether to provide an inclusive loop (current design) or switch to an exclusive loop, or perhaps something else. Ideally a loop would be "for i in sequence do .. done", so would work for any ordered set, not just integer subranges (see Python iterators). C for loop is too powerful to verify easily. Commented Dec 13, 2011 at 0:06
  • @Yttrill: I've edited my answer as an answer for your comment. Commented Dec 13, 2011 at 6:21
  • Re your edit, YES, I think I am looking at the problem from the wrong direction. The for loops are there because they're more restricted than the rather open-ended C for() loop, which is hard to check for correctness. I wanted something "more obviously correct" but I didn't really get it. [The purpose of Felix: it's a systems and application language designed to replace most C and all C++. I'm an ex-member of C++ committee so I have a good idea what's wrong with C++ :] Commented Dec 14, 2011 at 9:58