"Pascal" in this context seems to be "static typing with bounds checking" along with a handful of superficial syntactic similarities (but far more differences). You could substitute "Pascal" with a substantial subset of Algol-like languages and the comparison would make just as much (or little) sense.
Lazarus and Free Pascal have been around for an age, likewise Delphi for even longer. And they're all still here. Pascal adoption may have slowed, but it has always been here and no "return" is necessary.<p>Nice project though.
Previous discussion of this post: <a href="https://news.ycombinator.com/item?id=6316536" rel="nofollow">https://news.ycombinator.com/item?id=6316536</a>.<p>A longer thread about Nimrod: <a href="http://news.ycombinator.com/item?id=6272600" rel="nofollow">http://news.ycombinator.com/item?id=6272600</a>.
In a world with maps and folds do new languages really need for-loops? They seem like putting goto into a language as a fallback for uncommon performance cases and people who don't have the hang of higher order functions.<p>In particular, I don't like the fact the for-loops are often used in first examples. I had that issue when I looked at tutorials for D and Go for the first time. My initial reaction was "Seriously?"