[gjm11]

http://code.google.com/p/noop/source/browse/#hg/examples/noo...

but there's scarcely anything there. Which is all rather weird; I'd have thought that (1) one of the first things you do when designing a language is to mock up a load of example code to see how your ideas work together, and (2) you want to make that available to anyone looking at your language so that they can get a feel for what it's meant to be like. Oh well.

[DanielStraight]

Vaporlang?

[sethg]

That's my first impression--I see a bunch of pages on the project wiki with proposed features for the language, but no documentation along the lines of "if you actually want to use this language to accomplish something useful, here's what you do".

[jherdman]

Not only that but it looks incredibly underwhelming. It looks and smells so much like Java that you might as well use Java.

[gjm11]

I strongly suspect that something like this is the reason why there are few code samples. When do you not need to mock up lots of sample code when designing a language? When it's basically another pre-existing language with a few minor changes. (The pre-existing language in this case might not be Java, though I agree that that seems like a good guess.)

[cdibona]

Lordy, it's just a 20% project.