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

Enum doesn't occupy any space in an object?

7 posts in this topic

So,if I define an enum like:

 

class x{
public:
enum{
hey=0
};

}

 

Is it true that it doesn't occupy any space? And if yes,why?

0

Share this post


Link to post
Share on other sites

It's just a definition. Until you define a member variable it won't occupy any space.

 

class MyBigClass

{

    char aBigArray[1000000];

};

 

uses no space until you instantiate one (by decalring a variable of type MyBigClass).

Edited by Paradigm Shifter
2

Share this post


Link to post
Share on other sites

You are just telling the compiler you are going to use the symbol `x::hey' as meaning 0. That may or may not "occupy any space", depending on what exactly you mean by that. (The size of an object of type x will not be larger because of the enum, the executable will not be larger (except maybe for debugging info), but the source code will use more space, and the compiler will use more memory.)

Edited by Álvaro
0

Share this post


Link to post
Share on other sites

Thanks,got it.I was refering to using that code I showed you instead of a const inside a class.

 

So,Inside the class I could write int es[hey];

 

So should I use enums like that in a class instead of a static const if I need to write code like the array above? I understand that the performance I get by doing this is...very small,but just as a concept,is it better?

 

Ofcourse,I could just use int es[10],but when I need the same constant value in many places in a class,defining an enum like the one above,or a static const,might help understand the code faster.

Edited by noatom
0

Share this post


Link to post
Share on other sites

Variants of a compile-time constant has no effect on the run-time, because it is compile-time only. So not only is it very small, but exactly zero run-time performance difference. Design-wise... well, that's a different question and depends on what the constant is used for and what it represents.

0

Share this post


Link to post
Share on other sites
Enumerations should be used for groups of related values; if you're using a single-entry enum for a constant, you're going to confuse most people. I suggest sticking with actual constants instead.
2

Share this post


Link to post
Share on other sites
The code should reflect the intent as closely as possible. If you want a constant, use a constant.

Also, if you gave use a piece of code with meaningful identifiers, we would be in a much better position to make good suggestions.
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