• 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
  • entries
    195
  • comments
    198
  • views
    103657

New bug to me

Sign in to follow this  
Followers 0
SiCrane

482 views

I actually managed to run into a kind of bug in C++ that's new to me.

struct Base {
void print(void) {}
};

struct Derived : Base {
void print(void) {
Base:print();
}
};

int main(int, char **) {
Derived d;
d.print();

return 0;
}

Here Derived::print() wants to call the Base::print() function as part of its implementation. Unfortunately, this doesn't call Base::print(). Base: here is treated as a label before a recursive call to Derived::print() which causes a nice happy stack overflow.

On the plus side, this didn't show up in any actual production code. On the down side, it did show up in the sample exam questions the publisher supplied for a beginner's C++ book. You'd think that for a question along the lines of "what does this code snippet do" that someone would have actually tried compiling and running the code before deciding on an answer.

0
Sign in to follow this  
Followers 0


6 Comments


Classic. One of my favourites is:


class Fun
{
public:
int x;

Fun() {}
};

...

void someFunc()
{
Fun myfun(); // rather than "Fun myfun;"
myfun.x = 12;
}


Which will promptly tell you "left of .x must be a struct/class/union". Guess what? The empty constructor of the stack-allocated variable is treated as a forward declaration of a Fun-returning function with no arguments. This is amusing though, because adding one argument or more to the constructor will suddenly clear up the ambiguity and it will work as expected. [grin]
0

Share this comment


Link to comment
Quote:
Original post by SiCrane
Here Derived::print() wants to call the Base::print() function as part of its implementation. Unfortunately, this doesn't call Base::print(). Base: here is treated as a label before a recursive call to Derived::print() which causes a nice happy stack overflow.
Oddly, I had the same problem in some code I was writing yesterday:
gaPlayerLocal:;instance().enable(false);

That ended up calling the current classes instance().enable() function instead. It's one of these bugs you can stare at for hours and not see...

*sigh*
0

Share this comment


Link to comment
Quote:
Original post by HopeDagger
Classic. One of my favourites is:

Which will promptly tell you "left of .x must be a struct/class/union". Guess what? The empty constructor of the stack-allocated variable is treated as a forward declaration of a Fun-returning function with no arguments. This is amusing though, because adding one argument or more to the constructor will suddenly clear up the ambiguity and it will work as expected. [grin]


Love that one. Worse still in a similar vein is:


class c
{
public:
c(float a,float b){ }

void m(){ }
};

void g()
{
int i=10,j=20;

c v(float(i),float(j));
v.m();
}


The compiler mis-interprets the constructor-style casts as function parameters and treats the line as a local prototype.

You've got to love C++. [smile]
0

Share this comment


Link to comment
Quote:
Original post by SiCrane
... for a beginner's C++ book.

Which one?
0

Share this comment


Link to comment
Sad thing is, if you mix a lot of Lua programming with your C++ like I do, this kind of typo happens all the time since a single colon is the class method calling convention in Lua.
0

Share this comment


Link to comment
Nice. Rookie error.

Quote:
Original post by SiCrane
I actually managed to run into a kind of bug in C++ that's new to me.


How is this a 'kind of bug in C++'? As far as i can tell, its doing exactly what you're telling it to. Bug in code != Bug in compiler.
0

Share this comment


Link to comment

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