Hi people, It's been a long time since the last update to AngelScript, almost an entire month, and I ask forgiveness for this. I was busy making some extra money this month and had to put AngelScript to the side. Today I found some extra time so I decided to at least release a beta of the new version. There are a couple of minor interface changes for this version: - Two new methods in the asIScriptEngine, ExecuteString() and GetContextForExecuteString() - New parameter for ExecuteStep() in asIScriptContext If you are not using ExecuteStep() things should work just as before with a simple recompilation. If you use ExecuteStep() you should set the parameter to asEXEC_STEP_INTO (= 0) which is the only supported flag at the moment. In the next version ExecuteStep() will also support the flags asEXEC_STEP_OVER, and asEXEC_STEP_OUT_OF. ExecuteString() is a novelty that I'm currently finishing. It allows you to execute a simple string of statements using the currently compiled script code, perfect for situations like a Quake style console. Currently ExecuteString() cannot access the global script variables and constants, but all the rest is functioning, i.e script functions as well registered global properties and functions. The interface for ExecuteString() is the following: int ExecuteString(const char *script, asIOutputStream *out, int stackSize); script is the statements you wish to execute. You can execute more than one statement, separating them with ; but it is not necessary to terminate the string with ;. out is an output string that receives whatever errors are encountered during compilation of the string. stackSize is the size of the stack in the context the string will be executed. When this function is called the engine does a series of steps to execute the string: Wrap the string in a function. Compile the function. Create and prepare a context. Execute the context. The return value is either a negative value which indicates an error or one of the context states where the execution ended. If you wish to access the context created for this execution you can use the GetContextForExecuteString(). This can be used to resume the execution if it was somehow suspended, or to access exception information, etc. Stefan Diepenbrock was also kind enough to send me a makefile that should work with Linux gcc. Thanks Stefan. I will now go back to work and get the ExecuteString() to access global variables and constants as well. Regards, Andreas Jönsson Author of AngelScript --------- I've released the second beta of version 1.7.0. Changes for this version are: 1) ExecuteString() has a new parameter, a flag that can be either 0 or asEXECSTRING_ONLY_PREPARE. With asEXECSTRING_ONLY_PREPARE ExecuteString() compiles the string and prepares the context but doesn't execute it. To execute the string the application must use GetContextForExecuteString() and then call Execute() or ExecuteStep() on the context received. (thanks goes to Andrew "Desdemona" Wright for that idea) 2) ExecuteString() can now access global variables declared in the script. 3) I've transformed global script constants into read-only global script variables. This simplified the code a lot, however it may bring some compilation errors to your scripts in case you use global constants to initialize other global constants or variables. This also means that the compiler is no longer able to optimize operations with these global constants. I will redo the broken funcionality before the final release, but I think you would be interested in this interim release anyway because of the added funcionality. Regards, Andreas Jönsson Author of AngelScript -------- Global constant should now be working as before. I've even improved it a little. Now, global variables, being constant or not, can be initialized using expressions that use other global variables and global properties registered by the host application, they do not have to be constants. The order of initialization is depending partly on the order of declaration but also on dependency, i.e if a global variable "a" is being initialized with a variable "b" declared further down in the file, the initialization of "a" will be postponed until the used variable "b" has been initialized. Global variables can also be initialized with expressions using the condition operator ?:, the only thing that cannot be done is using the incremental operators, assignments, nor function calls. I've fixed a bug that prevented scripts from declaring global variables as pointers. Thanks Gunder Wulde for spotting that. A slight design flaw has been discovered Andrew "Desdemona" Wright, and that is related to function overloading. The problem is that a literal integer constant do not decide to use a function taking an int as parameter if there is also another function taking a float, in this case it gives an error reporting the two functions as multiple matches. Currently the solution is to manually cast to int, but I'll change AngelScript to give preference to a cast between int and uint over a cast between integer and floating point. There is yet another flaw where a pointer cannot be assigned a 0, if the pointer type is using behaviour functions. The problem is that the 0 isn't a reference. AngelScript will resolve this by placing the 0 in a temporary variable for the assignment. The next version fixing these two problems should be out any day now. Regards, Andreas Jönsson Author of AngelScript www.AngelCode.com ---------- This time I have what I hope is great news for all of you. I've decided to exchange the licensing form from LGPL to the zlib license, which means you are now free to statically link with the AngelCode Scripting Library without having to open source your own projects. I still would like a some credit in your projects for using the library though. That aside, I've also fixed the last missing points in the library before the final release. Namely: When finding the matching overloaded function, a conversion between signed and unsigned integers are given priority over conversion between integer and float (thanks Andrew "Desdemona" Wright) bug fix: A pointer with an assignment behaviour can now be assigned a null pointer. I will now take some time to update the manual for the real 1.7.0 release, and fix any bugs that might arise. When that is finished I will move on to version 1.7.1 which will support the different flags for the ExecuteStep() method. And after that I will bring in the concept of modules in version 1.8.0, which will allow applications to compile parts of the scripts under different namespaces, and also recompile the modules individually without affecting contexts running code from other modules. Regards, Andreas Jönsson Author of AngelScript __________________________________________________________ www.AngelCode.com - game development and more... AngelScript - free scripting library - Tower - free puzzle game [edited by - WitchLord on April 27, 2004 8:08:34 PM] [edited by - WitchLord on April 29, 2004 2:15:16 PM] [edited by - WitchLord on April 30, 2004 8:37:48 PM]

I was already using this technique of wrapping a function around a string. I had kept a seperate engine instance though. one word now - Yay!!!! hope we could get access to the 'environment variable' style global variables in the final version.

Will get back with comments. i would like to know if the full 1.7.0 can contain customizable strings for compiler output. would help a lot.

Jayanth.K

[edited by - EddHead on April 27, 2004 1:13:31 AM]

Desdemona:

Good idea, I''ll add that flag to the call.

EddHead:

I''m not sure what you mean with ''environment variable'' style global variables. Could you explain?

Currently the only way of having your own customized error messages are to open the source code and change the texts found in the as_texts.h file. If you have an idea for how to do this dynamically at run-time I''m ready to listen.



__________________________________________________________
www.AngelCode.com - game development and more...
AngelScript - free scripting library - Tower - free puzzle game

I''ve released the second beta of version 1.7.0. Changes for this version are:

1) ExecuteString() has a new parameter, a flag that can be either 0 or asEXECSTRING_ONLY_PREPARE. With asEXECSTRING_ONLY_PREPARE ExecuteString() compiles the string and prepares the context but doesn''t execute it. To execute the string the application must use GetContextForExecuteString() and then call Execute() or ExecuteStep() on the context received. (thanks goes to Andrew "Desdemona" Wright for that idea)

2) ExecuteString() can now access global variables declared in the script.

3) I''ve transformed global script constants into read-only global script variables. This simplified the code a lot, however it may bring some compilation errors to your scripts in case you use global constants to initialize other global constants or variables. This also means that the compiler is no longer able to optimize operations with these global constants.

I will redo the broken funcionality before the final release, but I think you would be interested in this interim release anyway because of the added funcionality.

Regards,
Andreas Jönsson
Author of AngelScript


__________________________________________________________
www.AngelCode.com - game development and more...
AngelScript - free scripting library - Tower - free puzzle game

It was a bug that made global pointers impossible. It will be fixed for the next release.

Thanks, for spotting that.

__________________________________________________________
www.AngelCode.com - game development and more...
AngelScript - free scripting library - Tower - free puzzle game

Oops what i meant i meant was that you will be able to use global variables properly, would mimic the dos-style environment variables. what i would like to see though is global constants which can be stored in the engine which can be accessed by any instance of the engine for ex: MOOD_AGGRESSIVE
or something like that

Jayanth.K
Raptor Entertainment Pvt. Ltd.
http://www.raptorentertainment.com

Global constant should now be working as before. I''ve even improved it a little. Now, global variables, being constant or not, can be initialized using expressions that use other global variables and global properties registered by the host application, they do not have to be constants. The order of initialization is depending partly on the order of declaration but also on dependency, i.e if a global variable "a" is being initialized with a variable "b" declared further down in the file, the initialization of "a" will be postponed until the used variable "b" has been initialized.
Global variables can also be initialized with expressions using the condition operator ?:, the only thing that cannot be done is using the incremental operators, assignments, nor function calls.

I''ve fixed a bug that prevented scripts from declaring global variables as pointers. Thanks Gunder Wulde for spotting that.

A slight design flaw has been discovered Andrew "Desdemona" Wright, and that is related to function overloading. The problem is that a literal integer constant do not decide to use a function taking an int as parameter if there is also another function taking a float, in this case it gives an error reporting the two functions as multiple matches. Currently the solution is to manually cast to int, but I''ll change AngelScript to give preference to a cast between int and uint over a cast between integer and floating point.

There is yet another flaw where a pointer cannot be assigned a 0, if the pointer type is using behaviour functions. The problem is that the 0 isn''t a reference. AngelScript will resolve this by placing the 0 in a temporary variable for the assignment.

The next version fixing these two problems should be out any day now.

Regards,
Andreas Jönsson
Author of AngelScript


__________________________________________________________
www.AngelCode.com - game development and more...
AngelScript - free scripting library - Tower - free puzzle game