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*

4
  • this post is rather hard to read (wall of text). Would you mind editing it into a better shape? Commented Oct 1, 2013 at 17:42
  • 1
    "There is a whole lot of design issues if you plan to see your programming language mainstream one day." I don't. But I'd still appreciate if you told me about the issues... Commented Oct 1, 2013 at 17:42
  • 1
    @gnat Thanks for pointing it out. Hopefully better now. Commented Oct 1, 2013 at 17:44
  • 1
    @AberKled I've tried to add a few. But as I told in the answer, take a look at the history of development of some mainstream language, better if it is driven by programming community nees rather than purists/elitists, to learn lessons from mistakes before making your own. Of course, do not forget main design goals for your language. Commented Oct 1, 2013 at 17:53