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

Problem declaring extern std::vector

10 posts in this topic

Hi, I 've no issues declaring a standard type vector as extern as follows:

[code]
extern std::vector<int> testVector; // main.h
std::vector<int> testVector; // main.cpp
[/code]

However, if I use a vector containing a custom structure, like follows, I get an "expected class name" error. See below:

[code]
extern std::vector<myTempObjects::myTempObjectLib> testVector; // main.h
std::vector<myTempObjects::myTempObjectLib> testVector; // main.cpp
[/code]

[code]
// myTempObjects.h
class myTempObjects : public mainClass { // ERROR expected class name on mainClass
Q_OBJECT
public:
myTempObjects ();
~myTempObjects ();
struct myTempObjectLib {
vector3_t hairControlPoint;
int r,g,b;
};
[/code]

Would you guys please teach me what's wrong? Thanks
0

Share this post


Link to post
Share on other sites
A definition of mainClass must be present at the point where you define the myTempObjects class. In other words, you probably need to #include "mainClass.h", or similar.

This doesn't have anything to with the extern declaration of the vector, as far as I can tell.
2

Share this post


Link to post
Share on other sites
You'll have to post a little more code then. Beforehand, you should try to simmer it down to the smallest possible piece of code that exhibits the problem.

99% of the time, in doing this you'll discover the problem for yourself. Should that not be the case, post back here.
1

Share this post


Link to post
Share on other sites
Though judging from your symptoms, I'd guess that your problem is circular inclusion: the headers that you're declaring your vector in is directly or indirectly included by the header that your class definition occurs in. Generally the way to fix this is by using forward declarations rather than full inclusion of headers whenever you can.
1

Share this post


Link to post
Share on other sites
If header A uses a class from header B, but only lets say a pointer, you dont need to include whole header B but only what is actually used from that header.

So instead of:
[CODE]
#include "B.h"
class AClass
{
BClass* pointer;
};
[/CODE]

you can simply do

[CODE]
class BClass; //There exists a class named BClass
class AClass
{
BClass* pointer;
}
[/CODE]


You only NEED to include the full header if you have a variable of that type which is not a pointer or reference, because in that case the class needs to know the size of the other class, for which it needs to full declearation. But since you use only a pointer, which is of fixed size, and do not use any of the functionality inside the class, all you need to do is to tell that the pointer is of type BClass so code outside the class with the pointer knows its type.
1

Share this post


Link to post
Share on other sites
In a.h:
[code]#pragma once
#include "b.h"

class B {
//...
};[/code]

In b.h:
[code]#pragma once
#include "a.h"

class A : public B { // <-- Possible problem!
// ...
}
};[/code]

Imagine a module that includes "a.h". It will expand the `#include "b.h"' into the text of the file "b.h" and it will reach the line `class A : public B' before it has seen B at all.

The solution I prefer is to not have header files that include each other like the two in my example. If at all possible, modules should provide services to the modules that use them, and not need to know anything about them. If you follow that advice, the inclusion graph is an acyclic directed graph and you won't run into the problem I just described.

In cases where two classes really need to know about each other, you can get around it using forward declarations. But this should really not happen very often.

Perhaps you have a header file that every module includes, where you can put things like global variables. That is a very tempting thing to do, but a really bad idea. Just don't do it.
1

Share this post


Link to post
Share on other sites
Hi guys, I'm still at trouble with this. Following your suggestions, and taking a look at the initial code I posted, I made a forward class declaration like this:

[code]class myTempObjects[/code];

But then how do I declare the extern vector? I tried the following and I'm getting a "incomplete type 'myTempObjects' named in nested name specifier"

[code]std::vector<myTempObjects::myTempObjectLib> myTmpObject; [/code]
0

Share this post


Link to post
Share on other sites
As someone mentioned before, "You only NEED to include the full header if you have a variable of that type which is not a pointer or reference, because in that case the class needs to know the size of the other class, for which it needs to full declearation".

So if you're using a vector of the actual classes (and not a pointer to the classes), you need the entire class definition - a forward declaration won't do.

As someone else suggested, I think the best thing to do it to try to make the smallest possible test case that reproduces the error - then we might be able to figure out what's going on.
1

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