• 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

Calling overriden Mixin

4 posts in this topic

Hi. I am really loving how mixin's are implemented, but I was wondering, When a class includes a mixin and overrides one of its member functions, Can we call the mixin's function explicitly anyway so we can extend its implementation? If not, would it be hard to add or break anything to add?

 

For example:

mixin class foo
{
    void print(){output("Hello");}
};

class bar : foo
{
    void print()
    {
        foo::print();
        output(" world!");
    }
};
0

Share this post


Link to post
Share on other sites

It would break what the mixin is smile.png

 

mixins are not inherited, as they are not real class declarations. They are more like macros to allow code reuse without having support for multiple inheritance in the language.

 

If you want to be able to call the mixin's implementation of a method, then the mixin's method should have a different name so it is included in your class.

0

Share this post


Link to post
Share on other sites

Yea, I just thought it would be nice to have the option to extend a default implementation instead of just override it. I guess I will just name it something else if needed, but then I need proxy functions for the 'default' implementation to get overridden. To achive the same, this is now needed:

mixin class foo
{
    void printfoo(){output("Hello");}
    void print(){printfoo();}
};

class bar : foo
{
    void print()
    {
        printfoo();
        output(" world!");
    }
};

I guess its not a big deal, it just seems annoying to have another layer of indirection for the 'default' behavior in this case especially since I doubt Angelscript can inline and eliminate the call for the default (presumably more often called) case. I guess it bugs me because one of the things I love most about Angelscript is how few proxy functions I need to write to get things done. Those always seemed so wasteful and ulgy to me. Code duplication is best avoided.

 

I understand they are macros instead of real inheritance , but why could the scope resolution operator not be allowed for them? Basically it would 'rename' mixin functions that have been overridden or just give them a 2nd name they can be accessed by. Or do these overridden functions not get compiled at all encase they now produce compile errors that are being avoided by the override?

 

It would bring them one step closer to being as useful as multiple inheritance without having to support MI, As multiple mixins could even have there own default implementations of the same function and the resulting class could pick what ones to call and in what order.

I actually like how mixins work more then MI, Mainly because it avoids the headache of virtual base classes in diamond inheritance when you want one variable to be accessible by multiple 'middle' classes to be derived from in various ways by other classes.

 

Of course, I don't know how complex this would be to add. I just thought if it was simple enough and didn't break anything, it might be considered but if not I can do without no problem.

0

Share this post


Link to post
Share on other sites

It's doable, but it would definitely not a trivial solution. I'll add a note on my to-do list to analyze this in detail for a possible future improvement.

2

Share this post


Link to post
Share on other sites

Awesome. That is all I can ask.

 

Also noticed the lack of constructors/destructors in mixins.. But I can understand that could get messy very quickly if used. So I'll stick to just adding functions for those if needed.

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