Sory for the trouble.
This is probably the last language feature - i am asking about .

whether "closures" are supported or atleast are in the immediate roadmap.

Actually, first moving into the task of exposing my C++ classes into angelscript, i need to make sure that the angelscript or any scripting language is apt for me.
Right now, i am evaluating between
NullC ( http://code.google.com/p/nullc )
and angelscript
and some other choices .
and the closures and exceptions are my main humble requirements from the scripting language or should atleast be in the immediate roadmap.
Thanks in advance

For further conceptual information on "closure", kindly refere to these url

closure in ruby
http://samdanielson.com/2007/9/6/an-introduction-to-closures-in-ruby



closure in nullC ( lua like smallsize language)
http://code.google.com/p/nullc/


closure in groovy
http://groovy.codehaus.org/Closures

closure in C#
http://csharpindepth.com/Articles/Chapter5/Closures.aspx

so , whether angelscript currently or in future support closure?

Sory for the trouble.
This is probably the last language feature - i am asking about .

whether "closures" are supported or atleast are in the immediate roadmap.

Actually, first moving into the task of exposing my C++ classes into angelscript, i need to make sure that the angelscript or any scripting language is apt for me.
Right now, i am evaluating between
NullC ( http://code.google.com/p/nullc )
and angelscript
and some other choices .
and the closures and exceptions are my main humble requirements from the scripting language or should atleast be in the immediate roadmap.
Thanks in advance

Looking at the links you provided, it does not seem like Angelscript supports closures natively. However, you could probably implement them yourself somehow. The language already supports function handles, which behave in a similar manner to C function pointers, but only for global functions at this time. Remember that whatever the language does not have you could always implement yourself without having to delve into the guts of the language yourself.

again thanks for the positive roadmap.
Closures are very much really needed for scripting language , esp.
They lead to lesser and lesser amount of code esp. in the GUI handling ,mathematical computation and maps,lists etc handling. Reduces the clutter and chances of bug by a lot.
The source code with closure also seem to very natural and logical .

again thanks for the positive roadmap.
Closures are very much really needed for scripting language , esp.
They lead to lesser and lesser amount of code esp. in the GUI handling ,mathematical computation and maps,lists etc handling. Reduces the clutter and chances of bug by a lot.
The source code with closure also seem to very natural and logical .

may i request you to keep a roadmap weboage on angelscript homepage(www.angelcode.com/angelscript )
the goals link (http://www.angelcode.com/angelscript/goals.asp ) there is different from upcoming/wishlist features , which will be a list of user's approved requests by you.
may be version number and feature can be given, but **no timeline** of the version number, if you can't promise so.
for example: http://groovy.codehaus.org/Roadmap

This will atleast keep users interested by having an opinion that "though this language has no feature X, but may be developer is interested, so i can start integration of my classes today, so that whenever that feature comes i will be ready." OR he may have an alternative opinion that "Though this language has no feature X, and this is essential for me, hence i should look for some other scripting language".
As in this thread in 2009 http://www.gamedev.net/topic/533245-1bind-static-member-func-2namespace-in-angelscript/ , you had said that namespace is on you todo list.


MOST IMPORTANTLY: by having this roadmap web page , If somebody needs a feature X which is already is in your approved roadmap(todo list), then he may financially contribute you/angelscript so that you can implement that feature 'early;.

Here is a sample roadmap like:
in roadmap These features may be in core or as an addon
namespace (version 3.1)
exception (Version 2.9)
autoboxing (version 2.9)
closure (version 2.7)

Not in roadmap:
mixin
multiple inheritance