Nice work, even if just for the learning experience. That said this seems remarkably similar to C or java with just a slight syntactic change. What advantage does your language have over say just writing a VM for C? Was there a reason you made your own over using one of the many out there? Not that there's anything wrong with that, just curious.

btw: I'm with Ectara and Ravyne, in that I like braces and semi-colons. I really don't like having forced formatting.

Well, the benifit of it is that even at this stage (just released version 0.03 bug fixes for compiler), you can grab it and make a simple 2d games with it (Check out the Break Out game I created with it, links on the project site). What I mean to say is, it is pretty straight forward and you don't need to learn anything else (graphic library like OpenGL or DirectX) beside language in order to write simple 2d games with the system. And since the syntax is very similar to C, anyone who has the knowledge of C, C++, java, or C# can just learn it in half an hour.

Another reason is portability, I am going to make VM for wide variety of devices.

Another reason is that it's open source, if you want any changes, you can tell me to add it (if I find it useful I will definitely add it) or just tweak the code yourself.

If the OP is still lurking around, here's my input:

Screw all this debate about semicolons and semantic whitespace and all the other religious nonsense that programmers will argue about.

Make the language you want to use. (Note that this is not the same as making the language you want to make. The idea of using it is critical.)

Thanks!!! That's what I plan to do.

This looks like an ambitious project. Making your own language is one of the best way to learn a lot of programming. And now and then it will make a contribution the the computer science. Keep up the good work!

1. Image as native data type? Wow. I made it a native-class in my system. I'd like to exchange some words on that.
2. operator+ operator-, "used to assign pointer". What is that? I see from the "pointer" description it's... I don't understand what. Some kind of autocast? It also seems to me your "pointers" are actually references.
3. I see you have while, but I don't see for. Oddly, I only have for, because I think it's more convenient. What made you take this decision?
4. I see your functions are like in C. To be honest, I think there's at least one very good reason to use the new func()->rettype syntax, which relates to type resolution. I'd like to hear your opinion!
5. Some functions in your standard library are fairly advanced (such as those involving drawing). By contrast, you have a "basic" rand(). Do you plan to improve support for random generation? In general, I'd like to hear something on your perspective for the future.
6. Are arrays a type or not? Can you inquiry about their contents/length etc?
7. I also thought using group instead of struct would make sense. But I couldn't quite make it (I actually only have class). What made you take this decision? I mean, struct is conventional wisdom (mere naming issue). Do you have support for functions taking a this pointer? (it appers not to me)
8. Inheritance. What's the result of group
   

   
   group Foo {
       int a;
   }
   
   group Oops : Foo {
       int a;
   }

9. You have threads? Man, that's outright scary! I mean, there are so much implications I don't even know where to start. Are you sure?
10. Are image objects "real"? I mean, if I assign an image object to another, will I copy all the pixels? That's going to be... well, like C++ I suppose.
11. Ok, there's startThread... and no other thread control?
12. I'm not even sure what's the deal with weak pointers.
13. You know what? I cannot actually do "Hello world" with per-frame changing color in my language ;)
14. Are you really sure you want to pass objects by value? It's a common source of grief in C++.
15. I'm afraid I don't understand the deal with passing by reference and group (in the "other" page).
16. Don't give people the layout of your image structure. Give them functions to operate on them as opaque data!
17. "If you use '=' copy one 'file' type to another, it will copy the address (like in the case of 'image' type)." What does that mean?
18. The way parameters are cast... it scares me quite a bit...
19. Ok, weakPtr is a cast. How does it work in the case of
    

    
    group Parent {
        int x, y;
    }
    
    group Child : Parent {
        int z;
    }
    
    void test(pointer Child p) {
        //body
    }
    
    Parent parent;
    test(weakPtr parent);
    

    I mean, it's a cast depending on function parameter type... to be resolved against overloading... ouch. And by the way, why should one downcast a struct to its parent?
    I guess I missed the part of the documentation in which you stated groups are passed always by reference. Perhaps that's what you meant a few points above?

Having my own lang as well I am very interested in hearing different opinions!

Also, Walter Bright, creater of the D programming language, just gave a

I don't want to derail, but yes I think its a very interesting language and its got the benefit of hindsight in both correcting and evolving the C lineage of languages. I've followed it for many years, but haven't yet done anything serious in it.

Every so often I get the create-a-language bug myself, but then I go looking for inspiration and D, Scala, and Haskell are so close to my high-level ideas (devil's in the details, of course) that I never follow through--I figure the amount of difference between these and any language I might create would be too small to justify the effort, and I've written plenty of parsers and small languages so its not even worth it as an accademic exercise for me. I mean, it's terribly interesting, but I'd just end up re-inventing one of these with slight changes and different syntax, and I've got better things to spend my time on.