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

Friend and adress function

5 posts in this topic

Maybe you're familiar with this but I'm not.Untill now I never saw a friend function.

Here's the code:

[source lang="cpp"]#ifndef TEXTUREMGR_H
#define TEXTUREMGR_H

#include "d3dUtil.h"
#include <vector>
#include <string>

class TextureMgr
{
public:
friend TextureMgr& GetTextureMgr();
typedef std::vector<std::wstring> StringVector;

void init(ID3D10Device* device);

// for debug
void dumpInfo()const;

ID3D10ShaderResourceView* getRandomTex();
ID3D10ShaderResourceView* createTex(std::wstring filename);
ID3D10ShaderResourceView* createTexArray(
std::wstring arrayName,
const std::vector<std::wstring>& filenames);

// .dds files can store cube textures in one file
ID3D10ShaderResourceView* createCubeTex(std::wstring filename);


private:
TextureMgr();
TextureMgr(const TextureMgr& rhs);
TextureMgr& operator=(const TextureMgr& rhs);
~TextureMgr();

void buildRandomTex();

private:
ID3D10Device* md3dDevice;

StringVector mTextureNames;
std::vector<ID3D10ShaderResourceView*> mTextureRVs;

ID3D10ShaderResourceView* mRandomTexRV;
};

TextureMgr& GetTextureMgr();

#endif // TEXTUREMGR_H[/source]

[source lang="cpp"]TextureMgr& GetTextureMgr()
{
static TextureMgr tm;

return tm;
}[/source]

In my book it says I can only have 1 texture manager.So a friend function gets acces to everything in a class,and that GetTextureMgr() also returns a TextureMgr type of object.

But why do we need an adress? friend TextureMgr& GetTextureMgr();

Can someone give me a good explanation?
0

Share this post


Link to post
Share on other sites
This is not an address (a.k.a. pointer), but rather a reference. But you would use both for the same reason: If you didn't use a reference (or pointer), you would actually return a copy of your TextureMgr (which is not what you want). By using a reference (the ampersand behind your type), you tell the compiler not to create a copy of your TextureMgr, but instead return the very same object to the caller of GetTextureMgr. This has nothing to do with the friend declaration. In the friend declaration, you just repeat the signature of the function you want to be a friend of your class. So, because your function has the signature "TextureMgr& GetTextureMgr()", you have to use "friend TextureMgr& GetTextureMgr()" in your class.

Now that we have the on-topic discussion done, here is some more advice: Even though your book tells you to use a singleton class (one for which there can only be one instance), this is in most cases (not in all, but definitely in this case) not the best (nor the easiest) solution to the problem. In fact, there is no reason not to allow a second texture manager, be it for another render target or so you can switch them out for different situations in your game. Also, this implementation of a singleton is a bit away from what most would consider a "default" implementation. But that's the least of its problems.

What book is this? It does not seem to teach a very clean programming style.
0

Share this post


Link to post
Share on other sites
Introduction to 3d game programming with directx 10

Also wouldn't it be enough just to decleare a static object of type texturemgr and use it everywhere I need it? It's pretty hard to understand what's going on here...



Sorry but i'm still very confused... Edited by noatom
0

Share this post


Link to post
Share on other sites
The friend declaration says that only that function is a friend. The functions declaration is:
[code]
TextureMgr& GetTextureMgr();
[/code]

Friending the function gives the function an access to its private constructors, since it can't be instantiated otherwise, and returns a reference to static TextureMgr object. Edited by Codarki
1

Share this post


Link to post
Share on other sites
If you just declare a variable somewhere you have absolutely no control over the initialization sequence. On the other hand, currently you know the singleton is initialized on the first call to GetTextureMgr, which is better.

Of course a singleton is still a singleton and a bad code smell is still a bad code smell, as rnlf already said.

Just to add, if something as fundamental a references gives you pause you should [i]really[/i] reconsider what you are doing. Learning C++ and learning 3D graphics at the same time is simply a recipe for disaster.
0

Share this post


Link to post
Share on other sites
you don't get me...i don't have a problem with references,I had a problem with using them when I decleare a function,I HAD....
0

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