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

Compiler behaviour quiz

8 posts in this topic

Here's some example code:

 

#include <iostream>
 
using namespace std;
 
struct number { float x; };
 
number test_func(void) { static number v; return v; }
 
int main()
{
    const number one = { 1.0f };

    test_func() = one;
    test_func().x += 1.0f;
    
    cout << test_func().x << endl;
    
    return 0;
}

 

Mini quiz:

 

1. Without using a compiler look at the code. Would you expect any warnings or errors from the compiler? Why?

 

2. What would you expect the output to be if it compiled?

 

3. Now compare your results to what actually happens when you compile it. Is it what you expected?

0

Share this post


Link to post
Share on other sites
your static is returned as a copy...

[edit]A nice compiler might warn you that your assignments are to a temporary, and won't have any real effect in this case. Edited by Hodgman
0

Share this post


Link to post
Share on other sites
If I haven't missed anything it should print "0" on all compilers.

Edit: And report no warnings or errors, except maybe about unused stuff. Edited by Rattenhirn
0

Share this post


Link to post
Share on other sites

[spoiler]

As you've hopefully found out by now on some compilers the code doesn't produce a single error or warning. This is the result from Clang:

 

test.cpp:14:19: error: expression is not assignable
    test_func().x += 1.0f;
    ~~~~~~~~~~~~~ ^

1 error generated.

 

I was expecting at least a warning from most compilers - the code is clearly not sensible. Clang didn't even pick up the other line of code that is equally bad...
[/spoiler]

1

Share this post


Link to post
Share on other sites

Good to know that there's yet another instance where Clang points out non sensical code. I'm not sure it's correct though, but too lazy to check it... :)

0

Share this post


Link to post
Share on other sites
Apparently GCC catches it also. Here's my expected results before compiling and before reading others' comments:

1. Without using a compiler look at the code. Would you expect any warnings or errors from the compiler? Why?

"test_func() = one;"- Some kind of 'Assigning to r-value/temporary' warning, since test_func() isn't returning by reference.
 
Also, test_func(void) should be test_func(), no need for the 'void' there. I don't know if a warning will result. Probably something like "explicit void argument - compile with -ANSI to disable warning"
 

2. What would you expect the output to be if it compiled?

Undefined gibberish value - whatever 'static number v' initially resolves to, because it has never been assigned anything.
 

3. Now compare your results to what actually happens when you compile it. Is it what you expected?

Using GCC/MinGW 4.7.2:
 
I didn't get the warning I expected on assigning "test_func() = one;",
instead I got an *error* on on the member variable assignment version: "test_func().x += 1.0f;"
 
error: using temporary as lvalue [-fpermissive]
 
[hr]
 
I only found out yesterday that this is valid and standardized C++:
const int &refToTemp = 357;
...it just only lasts to the end of the scope that the expression is contained in. Still it's useful for avoiding a copy in some circumstances, which is why I looked it up:
//Only makes a copy if 'condition' is false.
const std::string &myString = ( ...condition... ? this->memberString : this->GetCopyOfSubStr_ReturnByValue());
this->UseString(myString);
Edited by Servant of the Lord
0

Share this post


Link to post
Share on other sites

Also, test_func(void) should be test_func(), no need for the 'void' there.

(void) is a perfectly standard, legal alternative to () for function declarations that aren't destructors. It's not necessary, but neither is white space in most cases. Since (void) and () have a different meaning in C, giving a warning for this would annoy quite a few people who write or use headers that are meant to be used from both C and C++. And since that includes the C standard library headers, which every C++ compiler that is also a C compiler will have, this isn't a warning you'll find very often.

Undefined gibberish value - whatever 'static number v' initially resolves to, because it has never been assigned anything.

Objects with static storage duration, which includes function local static variables, are automatically zero-initialized before any other initialization takes place (if any). Since the class type lacks any implicit or explicit non-trivial constructors and the object has no other initialization, then zero initialization is the only thing that happens in this case.
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