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

Forward declared returned reference

3 posts in this topic

Hello,

 

I have a class like this:

class TabBarItem;

class TabBar :
    public Widget
{
public:
    TabBarItem& AddItem(const std::wstring& stText);
}

Now when I only include this header file and use that member method, I get this error under visual studio 2013:

error C2027: use of undefined type "acl::gui::TabBarItem"

when I use that method like this:

m_tabArea.AddItem(dock.GetName());

Storing the returned value in a reference fixes it:

auto& item = m_tabArea.AddItem(dock.GetName());

And so does including the headerfile of "TabBarItem". Why is this happening? I've had that issue for quite a while, and have always wondered. There is no copy being made even if I include the header file and leave the method without the assignement, and with pointers it works also. Is this some part of the specification or some obscure compiler error?

0

Share this post


Link to post
Share on other sites

You are probably failing to #include "TabBarItem.h" in the file that calls "m_tabArea.AddItem(dock.GetName());"

 

Maybe the compiler creates a temporary (non-reference) variable to receive the return result (?) since you aren't explicitly receiving it yourself, but then encounters a compiler error since "TabBarItem.h" was never included, and so it only sees the declaration and not the definition. (I'm guessing - I don't know if it actually creates a temp variable)

 

References and Pointers can be used without being fully defined (because the memory a reference or pointer takes is constant (sizeof(int&) == sizeof(MyLargeCustomType&)), regardless of the type), but an actual variable's size depends on the full definition that the compiler needs to know.

1

Share this post


Link to post
Share on other sites


You are probably failing to #include "TabBarItem.h" in the file that calls "m_tabArea.AddItem(dock.GetName());"

 

Sure, I did not explicitely write this, but I didn't fail to include it, I simply didn't want, since I didn't use the TabBarItem itself here. Thats the point of forward declaration, isn't it, if I wanted to have TabBarItem everywhere I only call methods of TabBar, I would have included it into TabBar.h.

 


Maybe the compiler creates a temporary (non-reference) variable to receive the return result (?) since you aren't explicitly receiving it yourself, but then encounters a compiler error since "TabBarItem.h" was never included, and so it only sees the declaration and not the definition. (I'm guessing - I don't know if it actually creates a temp variable)

 

Thats my only possible explanation, but why is this really happening? There is no sane reason for the compiler to do this, is there? I double checked, there is no copy constructor and/or destructor invoked here, so at least there is no "real" variable generated in this line. Why the compile error then? Its not that much of an annoyance, but more a WTF.

0

Share this post


Link to post
Share on other sites

http://msdn.microsoft.com/en-us/library/6c2dk0ah.aspx
 

It is possible to declare a pointer to a declared but undefined type. But Visual C++ does not allow a reference to an undefined type.

The following sample generates C2027.

 
// C2027_b.cpp
class A;
A& CreateA();

class B;
B* CreateB();

int main() {
CreateA(); // C2027
CreateB(); // OK
}

 

You're basically hitting a VC++ limitation with references to declared but undefined types.

2

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