String & unsafe references

Started by
3 comments, last by Tomashu 1 year, 5 months ago

Hello

After upgrading from 2.34 to 2.36 i get a lot of asserts on temporary variables. It only happens with option:

SetEngineProperty(asEP_ALLOW_UNSAFE_REFERENCES, 1);

For example in edited tutorial script:

string getA() { return "A"; }
string getA2() { return getA(); } // <--- 

float calc(float a, float b)
{
	Print(getA());
    return a * b;
}

It shows asASSERT( tempVariables.GetLength() == 0 ); in

> tutorial.exe!asCCompiler::CompileStatementBlock(asCScriptNode * block, bool ownVariableScope, bool * hasReturn, asCByteCode * bc) Line 1190 C++

Advertisement

Thanks for reporting this. I'll investigate and have it fixed as soon as possible.

Regards,

Andreas

AngelCode.com - game development and more - Reference DB - game developer references
AngelScript - free scripting library - BMFont - free bitmap font generator - Tower - free puzzle game

This problem has already been fixed in the latest WIP version along with some other bugs identified in 2.36.0.

Please give the latest WIP version a try and let me know if you're still facing issues.

Regards,
Andreas

AngelCode.com - game development and more - Reference DB - game developer references
AngelScript - free scripting library - BMFont - free bitmap font generator - Tower - free puzzle game

Thank you for your response. Everything works in WIP version ?

This topic is closed to new replies.

Advertisement