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

marvano

header!!

4 posts in this topic

hi, i just start using header file and i have some questions, do you guys know where i can find a good tutorial about header file? #include "whatever.h" do you find this line in other .h file? or those include only fit in .cpp? doing that i end including nearly all my .h in all my .cpp, i don''t think this is the best solution.. thanks for your help..
0

Share this post


Link to post
Share on other sites
header files are xactly the same as normal souce files xcept for a few diferences they usally just contain data type defintions and new frequently used funcitons. one thing u shoudl do is at the geigin of ure file do

#define "thenameofureheader.h"
#ifndef

put ure code here


#endif


this stop the code from being added twice into ure main file ie

#include "myheader.h"
#include "myheader.h" //will cause errors

void main()
{
}

~prevail by daring to fail~
0

Share this post


Link to post
Share on other sites
I don''t want to take away from what -Zerosignull- was saying, but considering that -marvano- isn''t even clear on how header files work, I feel I should help to explain it in more detail.

There are basically 2 types of files used in C/C++:
1.) header files (.h)
2.) implimentation files (.cpp)

Header files prototype the classes/functions/structures/etc that are contained within the implimentation file.
The implimentation file contains the code for the things that were prototyped in the header file.
For example:

---myprogram.h------------------------------------------
#ifndef _MYPROGRAM_H
#define _MYPROGRAM_H

//None of this will be included if
//_MYPROGRAM_H has already been defined.

int drawPoint(int x, int y);
char * getName();

#endif
--------------------------------------------------------

---myprogram.cpp----------------------------------------

#include "myprogram.h"

int main()
{
int i = drawPoint(7, 43);
//more code here.
return 0;
}

int drawPoint(int x, int y)
{
//This is the implimentation of my drawPoint function.
}

char * getName()
{
//This is the implimentation of my getName function.
}

--------------------------------------------------------

...what good is all of this? It illustrates what -Zerosignull- was saying about "stop the code from being added twice".
Header files are expanded into the implimentation file at compile time. Adding the #ifndef and #define in the header file tells the compiler to ignore everything up to the #endif (ignore it if _MYPROGRAM_H has been defined), thus preventing multiple definitions/redefinitions of functions/classes/etc if you included the same header file multiple times.
In other words:

#include "myfile.h"
#include "myfile.h"
#include "myfile.h"

...all 3 are expanded into the CPP file, but the compiler only really looks at the 1st one, the other 2 are ignored.
I hope this helps.
0

Share this post


Link to post
Share on other sites
so i am not clear huh? (just kidding)

Ok, I did''n know that, thanks, but my question is,
Is it normal to have a LOT of #include in all .cpp, or there is another way to regroup everything?


(I am french speaking so that''s why i am *maybe* not clear as i wish..

marvano

0

Share this post


Link to post
Share on other sites
when you are new you will have to have lots of .h files included in all of your .cpp files, as you get better you will figure out how to use fewer. When you are new you will also have a lot of .h files in your other .h files. You should learn how to cut that down too. You should use forward declarations for classes whenever possible, but if you aren''t passing by pointer or if you are calling member functions you''ll probably have to include the .h file.
0

Share this post


Link to post
Share on other sites