• Advertisement

Papirosnik

Member
  • Content count

    12
  • Joined

  • Last visited

Community Reputation

125 Neutral

About Papirosnik

  • Rank
    Member
  1. Hi. I've successfully registered all methods of my class. Here is one of them. void addNode(Node* node, const Point& pos);void addNode(Node* node, int x = 0, int y = 0);....r |= ase->RegisterObjectMethod(name, "void addNode(Node@, int, int)", asMETHODPR(T, addNode, (Node*, int, int), void), asCALL_THISCALL);IwAssert(SCRIPT, r >= 0); when I'm trying to invoke this method in my angel code I get the following error: *** ERROR: No matching signatures to 'cScene::addNode(Texture@&, const uint, const uint)' Candidates are: void cScene::addNode(Node@, const Point&in) void cScene::addNode(Node@, int, int) Here is that angel code:void onReset(){ Texture@ tex = ResManager.getTexture("back", "options"); Scene.addNode(tex, 320, 0);}Why 320 and 0 are treated as const uint when I assume that they actually are int ? Thanks. PS. Just after posting this topic I've found my stupid mistake ). Texture@ cannot be casted to Node@. The shame on my head. Excuse me, please, and delete this topic at all!
  2. Compiling for Marmalade SDK

    Hi, Andreas. As I said many times - I love AngelScript 2,25,2 is fine. only there is another kind of warnings in case we are not using threads in marmalade: [CODE]1>d:\_prj\_thestack\src\age\3rd_party\angelscript\source\as_thread.cpp(75): warning C4390: ';' : empty controlled statement found; is this the intent? 1>d:\_prj\_thestack\src\age\3rd_party\angelscript\source\as_thread.cpp(81): warning C4390: ';' : empty controlled statement found; is this the intent? 1>d:\_prj\_thestack\src\age\3rd_party\angelscript\source\as_thread.cpp(87): warning C4390: ';' : empty controlled statement found; is this the intent? 1>d:\_prj\_thestack\src\age\3rd_party\angelscript\source\as_thread.cpp(93): warning C4390: ';' : empty controlled statement found; is this the intent?[/CODE] It is such little trifle that we should not talk about it But my love have to be perfect)))
  3. opEquals now doen't work

    Notice also as_scriptengine.cpp(3586): warning : 'stdcall' attribute directive ignored [CODE]1>------ Build started: Project: TheStack_vc10, Configuration: GCC ARM Release Win32 ------ 1>Build started 11/20/2012 12:23:54 PM. 1>InitializeBuildStatus: 1> Creating "Release_TheStack_vc10_gcc_arm\TheStack_vc10.unsuccessfulbuild" because "AlwaysCreate" was specified. 1>CustomBuild: 1> All outputs are up-to-date. 1>ClCompile: 1> ARM Compiling(GCC) d:\bumper\_prj\_thestack\src\age\3rd_party\angelscript\source\as_scriptengine.cpp ... 1> d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/source/as_scriptengine.cpp( In member function 'void* asCScriptEngine) ::CallGlobalFunctionRetPtr(asSSystemFunctionInterface*, asCScriptFunction*)': 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/source/as_scriptengine.cpp(3586): warning : 'stdcall' attribute directive ignored 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/source/as_scriptengine.cpp(3586): warning : 'stdcall' attribute directive ignored 1> 1> 1> d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/source/as_scriptengine.cpp( In member function 'void* asCScriptEngine) ::CallGlobalFunctionRetPtr(asSSystemFunctionInterface*, asCScriptFunction*, void*)': 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/source/as_scriptengine.cpp(3607): warning : 'stdcall' attribute directive ignored 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/source/as_scriptengine.cpp(3607): warning : 'stdcall' attribute directive ignored 1> 1> 1> d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/source/as_scriptengine.cpp( In member function 'void asCScriptEngine) ::CallGlobalFunction(void*, void*, asSSystemFunctionInterface*, asCScriptFunction*)': 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/source/as_scriptengine.cpp(3707): warning : 'stdcall' attribute directive ignored 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/source/as_scriptengine.cpp(3707): warning : 'stdcall' attribute directive ignored 1> 1> 1> d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/source/as_scriptengine.cpp( In member function 'bool asCScriptEngine) ::CallGlobalFunctionRetBool(void*, void*, asSSystemFunctionInterface*, asCScriptFunction*)': 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/source/as_scriptengine.cpp(3727): warning : 'stdcall' attribute directive ignored 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/source/as_scriptengine.cpp(3727): warning : 'stdcall' attribute directive ignored 1> 1> 1> d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/add_on/scriptstdstring/scriptstdstring.cpp( In function '_STL) ::string formatInt(asINT64, const _STL::string&, asUINT)': 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/add_on/scriptstdstring/scriptstdstring.cpp(344): warning : comparison between signed and unsigned integer expressions 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/add_on/scriptstdstring/scriptstdstring.cpp(345): warning : comparison between signed and unsigned integer expressions 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/add_on/scriptstdstring/scriptstdstring.cpp(346): warning : comparison between signed and unsigned integer expressions 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/add_on/scriptstdstring/scriptstdstring.cpp(347): warning : comparison between signed and unsigned integer expressions 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/add_on/scriptstdstring/scriptstdstring.cpp(348): warning : comparison between signed and unsigned integer expressions 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/add_on/scriptstdstring/scriptstdstring.cpp(349): warning : comparison between signed and unsigned integer expressions 1> 1> 1> d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/add_on/scriptstdstring/scriptstdstring.cpp( In function '_STL) ::string formatFloat(double, const _STL::string&, asUINT, asUINT)': 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/add_on/scriptstdstring/scriptstdstring.cpp(388): warning : comparison between signed and unsigned integer expressions 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/add_on/scriptstdstring/scriptstdstring.cpp(389): warning : comparison between signed and unsigned integer expressions 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/add_on/scriptstdstring/scriptstdstring.cpp(390): warning : comparison between signed and unsigned integer expressions 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/add_on/scriptstdstring/scriptstdstring.cpp(391): warning : comparison between signed and unsigned integer expressions 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/add_on/scriptstdstring/scriptstdstring.cpp(392): warning : comparison between signed and unsigned integer expressions 1> 1> 1>d:/bumper/_prj/_thestack/src/age/3rd_party/angelscript/add_on/scriptstdstring/scriptstdstring.cpp(393): warning : comparison between signed and unsigned integer expressions 1> 1> 1>Link: 1> ARM Linking(GCC) ... 1> TheStack_vc10.vcxproj -> d:\Bumper\_Prj\_TheStack\bin\TheStack.s3e 1>PostBuildEvent: 1> D:\Marmalade\6.1\s3e\python\python.exe .\process_map.py "d:\Bumper\_Prj\_TheStack\bin\TheStack.s3e" 1>FinalizeBuildStatus: 1> Deleting file "Release_TheStack_vc10_gcc_arm\TheStack_vc10.unsuccessfulbuild". 1> Touching "Release_TheStack_vc10_gcc_arm\TheStack_vc10.lastbuildstate". 1> 1>Build succeeded. 1> 1>Time Elapsed 00:01:08.01 ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========[/CODE]
  4. opEquals now doen't work

    I've tested 1474 revision. it seems all works properly..... The comments are correct from now Fake warnings about memory leaks went away...although There is a lot of warnings about comparison between signed and unsigned integer expressions for example in scriptsstdstrings.cpp: bool leftJustify = options.find("l") != -1; I also wrote earlier so because it is very short and convenient way. But marmalade gcc compiler doesn't like such scriptures. It wants something like this: bool leftJustify = options.find("l") != std::string::npos; or at least bool leftJustify = options.find("l") != 0xFFFFFFFF; Those warnings can be boldly ignored But their count is significant and between them may be overlooked some important warnings PS. MS VS compiler silently permits those comparisons.
  5. Marmalade: Angelscript runs fine on x86, crashes on ARM

    [quote name='Andreas Jonsson' timestamp='1352988835' post='5001224'] Thanks. I think I'll try the # style then. It would be good if someone using Marmalade can confirm that it actually works before I check in the changes. [/quote] I just checked and can confirm that '//' comments are not allowed; using '#' instead '//' is allowed but only at the beginning of the line... arm assembler uses '#' as a part of operands. '/*.. */' is allowed everywhere and probably would be the best solution.
  6. opEquals now doen't work

    [quote name='Andreas Jonsson' timestamp='1353073757' post='5001537'] I think you'll agree with me that it is not a very nice solution. [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img] [/quote] Yes, of course. ) And advantages of AngelScript are so strong that we can close our eyes even if there will be real memory leaks. Thank for your work. Have fun with your creativity.
  7. opEquals now doen't work

    what's about namespace and/or unique names? [CODE]namespace AngelScript { ststic string dummyStringForStringFactoryRoutineToAvoidProblemsWithMarmaladeMemoryManager; // } static const string &StringFactory(asUINT length, const char *s) { ... AngelScript::dummyStringForStringFactoryRoutineToAvoidProblemsWithMarmaladeMemoryManager = ""; ... }[/CODE]
  8. opEquals now doen't work

    Yes, you are right. With marmalade we need to initialize graph unit via IwGxInit invoking and finalize it before the completion of the application (via IwGxTerminate). and the marmalade memory manager is initialized and finalized inside this functions. We cannot affect it and static objects are freed after the memory manager has completed its work. But my workaround for some reason works. You are not forced don't use static string variable. My suggestion is just declare it a bit in another place. Thank you anyway.
  9. opEquals now doen't work

    Andreas, thank you for your answer. operator!= is thrown now from the registration list ) About memory leak...actually there is no real memory leak there. But if some memory deallocations on the heap occur after the marmalade memory manager finalization - it considers that there is a memory leak. Many of static objects (on the heap) will be deallocated after last line of code (where memory manager will be finalized). The order of their allocation/deallocation may be a bit confusing. And Marmalade developers cannot do anything with such static objects behaviour. The only thing that they can do is to recommend don't use static non-POD objects. So I'm happy that I managed to find the workaround that allows to shut up that annoying assertions. I am sure that the windows with assertions about memory leaks irritate not only me (someone can even get scared).
  10. Marmalade: Angelscript runs fine on x86, crashes on ARM

    I have to say also that angelscript can work properly with marmalade.. with some finishing touches. Firstly, .S file can't contain c++ comments (I wrote about this here: http://www.gamedev.net/topic/626036-compiling-for-marmalade-sdk/) Secondly, it needs to use scons for Android or IOS builds (see http://www.madewithmarmalade.com/devnet/forum/angel-script for more details).
  11. opEquals now doen't work

    Hi. I've got one question and one suggestion (not related). [b]The questions[/b] is: What happened with opEquals operator? In earlier versions this code worked properly: [CODE]r |= ase->RegisterObjectMethod("Color", "bool opEquals(const Color &in) const", asMETHODPR(Color, operator==, (const Color &in) const, bool), asCALL_THISCALL); r |= ase->RegisterObjectMethod("Color", "bool opEquals(const Color &in) const", asMETHODPR(Color, operator!=, (const Color &in) const, bool), asCALL_THISCALL);[/CODE] But in 2.25.1 I get r = -1 after execution of the second line. How can I get working operator!= ? [b]the suggestion[/b]: I use angelscript within marmalade sdk and upon the whole all works fine...excluding one moment: The marmalade memory manager doesn't like static non-POD (plain of data) objects. Often in that case It detects that there are some memory leaks. Are there really memory leaks or not - I can't judge, but those assertions are annoying. In particular, within StringFactory function (scriptstdstring.cpp) there is such line: static string dummy; Marmalade memory manager considers that here is memory leak. My workaround is take out this line from StringFactory body: [CODE]static string dummy; static const string &StringFactory(asUINT length, const char *s)[/CODE] I can't say why this workaround works but it works. Now marmalade doesn't see any memory leaks.
  12. Compiling for Marmalade SDK

    Hi, Andreas. When I was compiling Angel Script with gcc-arm for using with the Martmalade SDK I have noticed that that compiler doesn't recognize comennts in c++ style in the as_callfunc_arm_gcc.S. At once I have removed all '//' and '/* */' all was compiled successfully. It is a feature of that compiler or maybe I have missed something? It's slightly inconvenient to remove those comments every time after refreshing from git.
  • Advertisement