• 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
pressgreen

Vector MADNESS

9 posts in this topic

Ok, what is the best way to access the last element of the vector i just populated? So in the same function I push a matrix on to that vector and I then want to use that matrix and multiply it against another matrix. what would be the best approach of doing this?

 

 

vector<Matrix> MatStack;

 

MatStack.push_back(newMatrix);

 

MatStack[MatStack.Size()] * differentMatrix;

 

or

 

MatStack[MatStack.Size() - 1] * differentMatrix;

 

 

0

Share this post


Link to post
Share on other sites
I wouldn't go so far as to say always check (and certainly not with all caps). It's safe to access back() or vec[vec.size() - 1] right after using push_back() on the vector or using other operations that add elements or set the vector to a known non-zero size. Since std::vector uses exceptions to signal errors for things like insertions, control flow simply won't reach an illegal access in those cases. If feeling paranoid you can add a debug assertion for those cases when you do assume the vector isn't empty, but most standard library implementations already put a debug assertion in operator[] for vector.
2

Share this post


Link to post
Share on other sites

I wouldn't go so far as to say always check (and certainly not with all caps). It's safe to access back() or vec[vec.size() - 1] right after using push_back() on the vector or using other operations that add elements or set the vector to a known non-zero size. Since std::vector uses exceptions to signal errors for things like insertions, control flow simply won't reach an illegal access in those cases. If feeling paranoid you can add a debug assertion for those cases when you do assume the vector isn't empty, but most standard library implementations already put a debug assertion in operator[] for vector.

 

I strongly agree with this.

 

It can be a little overhead in checking vector size validity in situations where you absolutely sure that it's size cannot actually be zero.

0

Share this post


Link to post
Share on other sites


I wouldn't go so far as to say always check (and certainly not with all caps). It's safe to access back() or vec[vec.size() - 1] right after using push_back() on the vector or using other operations that add elements or set the vector to a known non-zero size. Since std::vector uses exceptions to signal errors for things like insertions, control flow simply won't reach an illegal access in those cases. If feeling paranoid you can add a debug assertion for those cases when you do assume the vector isn't empty, but most standard library implementations already put a debug assertion in operator[] for vector.

 

I strongly agree with this.

 

It can be a little overhead in checking vector size validity in situations where you absolutely sure that it's size cannot actually be zero.

 

This is true. I'd just add that since someone else (or you) may come along later and not notice the logical guarantee, it may be a good idea to add a comment in cases where it's not immediately apparent from looking at the code.

Edited by Khatharr
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