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

Archived

This topic is now archived and is closed to further replies.

Weston

New struct (to me)

3 posts in this topic

I was reading through Tricks of the Windows.... yada yada yada... and in one chapter reguarding bitmaps, there is a new structure setup I''ve never seen. I looked through my C++ books and couldn''t find anything similar to it. I suppose it''s more of a C thing, so here it is: typedef struct tagBITMAP_FILE { BITMAPFILEHEADER bitmapfileheader; BITMAPINFOHEADER bitmapinfoheader; PALETTEENTRY palette[256]; UCHAR *buffer; } BITMAP_FILE, *BITMAP_FILE_PTR; I understand the need for typedef and the tag, but the two variables at the bottom have me questioning. In C++, minus the typedef, this would make BITMAPFILE and BITMAP_FILE_PTR objects. But they don''t work like objects in the previous definition, but rather like a type instead. What I want to know is what is going on here, and is there a more C++ like way to rewrite the structure? I''d like to be able to work with a more familiar syntax.
0

Share this post


Link to post
Share on other sites
Just a shorthand way of defining types (note the keyword typedef)

another way is to write:

struct tagBITMAP_FILE
{
BITMAPFILEHEADER bitmapfileheader;
BITMAPINFOHEADER bitmapinfoheader;
PALETTEENTRY palette[256];
UCHAR *buffer;
};

typedef struct tagBITMAP BITMAP_FILE;
typedef struct tagBITMAP *BITMAP_FILE_PTR;

0

Share this post


Link to post
Share on other sites
quote:
they don't work like objects in the previous definition, but rather like a type instead

Exactly!

As types there is no longer a need for the "struct" keyword

BITMAP_FILE bmp;
BITMAP_FILE_PTR bmp_ptr = &bmp;


quote:
is there a more C++ like way...


Sure, turn the struct into a class.





Edited by - lessbread on February 17, 2002 11:30:14 PM
0

Share this post


Link to post
Share on other sites
Imagine you are declaring a variable ''i'' to be of type int.
int i; // ''i'' is an ''int'' 

If you add the keyword typedef, you suddenly declare ''i'' to be the type int.
typedef int i; // ''i'' means ''int'' 


Now, when declaring a struct, you can immediately declare a variable of the struct type by putting variable names after the struct declarations, just as you do with ''int'' or other types.
struct TAG {...} var1, var2, *var3; 


Furthermore, when you know you won''t need other variables of that type, you can omit the tag and declare an anonymous struct :
struct {...} var1, var2, *var3; 


Remember that, as far as pointer declarations go, the ''*'' is associated with the variable name, not with the type (i.e, ''int *i'' really means ''int (*i)'', not ''int* i''). Thus ''int *i, j'' makes ''i'' a pointer to int and ''j'' an int (instead of two pointers).

So the same is true with your struct : BITMAP_FILE and BITMAP_FILE_PTR would be (without the typedef) respectively a variable of type ''struct tagBITMAP_FILE'' and ''pointer to struct tagBITMAP_FILE''. But with the typedef keyword, you are no longer declaring a variable, but a type, so they become aliases for (respectively) ''struct tagBITMAP_FILE'' and ''pointer to struct tagBITMAP_FILE''.

However, as LessBread pointed out, now C++ compilers will let you use the unqualified tag (i.e. tagBITMAP_FILE) as an alias for the full type name (struct tagBITMAP_FILE).
0

Share this post


Link to post
Share on other sites