Quote:Original post by jetro
Pointers and syntax stuff related to them are hard to understand for beginning/novice coders. Because of this I'd also like the '->' operator go away and have just '.' instead - it works pretty well with Java already. :)

That's why in my application when the user type '.' it is automaticaly changed to '->' if needed.

To express myself on this subject more than with a angry face, this is my full point of view, and why it make me "monter la moutarde aux nez quand je lis ce genre de truc" sorry I cant translate.

Why did I choose AS :
I have tried LUA with ToLUA++. The integration of LUA in my project was pretty easy. Everything was working well when there come time to make script. The LUA language make me search for another scripting library that was much "natural" to write script with.
I have integrated the VBScript engine in another project, and definitively this was not the solution, or I had to write COM handler for all the classes I wanted to insert into VBScript.
So, as I was looking for AS for longtime ago, I have decided to give it a try.
The integration of AS was pretty easy, and script was also easy to write. So I have choosed it (from 1.8.x).

Then time passed, and AS has become to change.
The library has changed the include path to angelscript.h . Of course this is not a pb, but with a source controled project this is not good. So now every time I want to integrate a new version, I have to change the include of as_xxxxx files that point to the new path.
This is not a pb ...

Time has passed and I have integrated AS in a much closer way than more of AS user has did (I think). I have make my own asIScriptEngine derived class to be able to process registered func/var/class/method that let the script write get tool tips that help to write script with syntax hilight and other feature.
The library then has change the asISScriptEngine interface !

Nowaday, I've got a fully working application, with lot of script using it and it's about to change a CORE functionnality !

Quote:Original post by Desdemona
I have the unfortunate feeling that the change will wrack with my current game since it is so dependant on AS. I am using 1.9.2 and am almost finished with my engine. Everything is working perfectly so I have not had any intentions of upgrading, but I'd probebly take a stab at it for simpler syntax.

This resume perfectly my feeling.

No library is perfect. This is a fact !

AbrKen

Hi WitchLord

Im using AS with tons of pointers functionality (but as you know, a very modified AS 1.8.2b1 version as well, so im not using the as a lib but more like an engine integrated directly in my project), but here we need to look for what is best for the library future, so i know that changing how pointers are handled will make the library better/easy for new features to implement. So pointers need to be changed, and what you are saying is a good way of handle them in a script (im a little worried about the perfomance, well you know me :) )

Most of the users of a script library will use it for giving his application the ability of be modified/improved by final users, and here is where pointers are a bit of a problem, as new users or non-technical users can have problems

I dont know why there are complaints about changing pointers, if what is going to change is mostly the interface, not the CORE, and if this change will benefit the library as well the end users/script writters, this is a good direction to go, because at the end, this (end users) will be the factor that make our projects a success

Changing them in AS 1 or implementing in a new AS 2, either way, but its some that have to be done

Best Regards,

Lioric

Don't worry about my opinion, it's just mine.

Change your lib as you want.

I've been following AngelScript for awhile now, and have been taking some Java classes recently. While I hate Java as a language, I think it would be awesome to see the way they handle Objects in AngelScript. And anything that can speed up the library is always a plus.

Would it be possible to integrate smart pointers into this? It would remove the need to have raw pointers, what I'd like to have is the possibillity to just use it like Class->Method when Class is actually a smart pointer.
I am not sure if this would still allow you to simplify AS as a whole, but if it was, this would be nice. Shouldn't be too hard either, basically there'd just need to be some way to register a function for the script engine that would allow it to retrieve the actual class on which it would then execute the method.

Quote:Original post by Wuntvor
Would it be possible to integrate smart pointers into this? It would remove the need to have raw pointers, what I'd like to have is the possibillity to just use it like Class->Method when Class is actually a smart pointer.

Personally, I think if you're going to remove pointers from the script, you should also remove the operator->. This would simplify the the syntax of the language, as it can only be used with pointers (since I belive AS doen't allow you to overload operator-> in your classes.)

Just my thoughts on the matter though.