• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
BlackMoons

asIScriptObject::Release return code

9 posts in this topic

Hi. Today I managed to accidentally access a null handle in a Angelscript destructor called by my C++ program calling asIScriptObject::Release() on a script class object passed from Angelscript to C++.

 

The problem? It never logged anything in my error logs.

I go and check Release()'s return code and its 0.

 

Shouldn't it be returning asEXECUTION_EXCEPTION? And then I could handle it the same way as when Context->Execute() hits a null handle?

0

Share this post


Link to post
Share on other sites
asIScriptObject::Release returns the number of remaining references to the object. In your case it returned zero so you released the last one which destroyed the object.

You're not really meant to use the return value from Release or AddRef. These are only returned for debugging purposes.

You only need to know that after calling Release you should no longer access the object from that pointer.
0

Share this post


Link to post
Share on other sites

Ah, Then how should I detect when calling Release() results in a script exception and script execution of destructors being abandoned early?

 

I do understand that an exception in a destructor is a very bad thing that should be avoided at all costs due to potential for resource leaks, but that is exactly why I need to detect when it occurs so I can report the error and shut down the program so the code itself can be fixed.

Edited by BlackMoons
0

Share this post


Link to post
Share on other sites

On exception, Raise a bool flag in the context, Allow checking that bool and if true they can get info of the exception using the normal script exception mechanism.

 

Yea, its kinda ugly, But something has to be done to allow it.

 

It might also allow people to have a centralized cache in there main loop for angelscript errors encase they ever forget to check the return code of normal executes(), or some other process raises an unexpected exception.

 

It beats a callback in that you can at least handle the error where it occurred and have some state information if you just assert()/log to text file on it or similar.

0

Share this post


Link to post
Share on other sites

The problem is that the context that executes the destructor may not even be known by the application. If it is the garbage collector that calls it, then the garbage collector will create its own context for that execution.

 

I need to figure out a clean way of letting the application know about this internal context so that the application can set the exception callback, and even the line callback to allow the debugging of the destructor call.

0

Share this post


Link to post
Share on other sites

The way I'm thinking about solving it is by having the engine invoke a callback from the application whenever it needs a context to execute some script code internally. The application can then supply a context that has been set up with the appropriate callbacks for catching exceptions. Not only would the application be able to report exception in the destructor this way, but it would also be able to debug the execution, and better pool the contexts to improve performannce.

 

It would also work better in a multithreaded environment as you could potentially have multiple contexts in parallel.

 

Of course, the application callback would be optional and if not provided the engine would create the context on its own as it currently does.

0

Share this post


Link to post
Share on other sites

Ah that would be nice. Yea I would prefer that angelscript just reuse the one context I have with push/pop state and minimize run time allocations.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0