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

Declaring class objects as a pointer or not

10 posts in this topic

I was reading that dynamically creating class instances can cause problems included fragmentation.

I was jsut wondering if it was reccomended to people with less experience to declare instances like this:

MYCLASS myClass;

rather than:

MYCLASS* myClass;

?

thanks,
0

Share this post


Link to post
Share on other sites
Using pointers is more work, more code and increased risk for mistakes so I always avoid pointers unless there is a good reason to use pointers.
0

Share this post


Link to post
Share on other sites
[quote name='Wooh' timestamp='1312762339' post='4845970']
Using pointers is more work, more code and increased risk for mistakes so I always avoid pointers unless there is a good reason to use pointers.
[/quote]

If you aren't using pointers the object itself is getting saved on the stack. So you should always use pointers. This way only the pointer variable itself is located on the stack and the object is located on the heap. That's it.
-2

Share this post


Link to post
Share on other sites
[quote name='CryZe' timestamp='1312768837' post='4846010']
If you aren't using pointers the object itself is getting saved on the stack. So you should always use pointers. This way only the pointer variable itself is located on the stack and the object is located on the heap. That's it.
[/quote]

And how is that a good thing, unless your object is really huge (as in "size expressed in kb - mb")? "Allocating" stack just does something like stack_ptr -= sizeof(Object)

In comparison new will deal with the OS, take a ton more time for allocation, add the potential for bugs and memory leaks and unless the object is needed beyond that function serves no practical or performance oriented purpose I could see.

And in regard to the original question: either you need your object on the heap or not. If you do, then declaring a pointer is useless, because you _still_ need to create the actual object somewhere. Avoiding fragmentation requires a little more work and design than just adding a *. If you're talking about temporary objects in a function: the stack doesn't fragment.
0

Share this post


Link to post
Share on other sites
[font=arial, verdana, tahoma, sans-serif][size=2][quote name='lukesmith123' timestamp='1312761389' post='4845962']To declare class objects as a pointer or not?[/quote]It depends.[/size][/font]
0

Share this post


Link to post
Share on other sites
[quote name='CryZe' timestamp='1312768837' post='4846010']
[quote name='Wooh' timestamp='1312762339' post='4845970']
Using pointers is more work, more code and increased risk for mistakes so I always avoid pointers unless there is a good reason to use pointers.
[/quote]

If you aren't using pointers the object itself is getting saved on the stack. So you should always use pointers. This way only the pointer variable itself is located on the stack and the object is located on the heap. That's it.
[/quote]

That's not true. If the variable is declared inside a heap-allocated class instance as a non-pointer, it will still be allocated on the heap. If you're inside function scope then sure, the variable will be allocated on the stack. Recommending someone to always use pointers is quite a blanket statement however.
0

Share this post


Link to post
Share on other sites
Don't use raw pointers unless you have a good reason to do so.
Don't allocate on the heap unless you have a good reason to do so.

You can allocate on the heap without dealing with raw pointers

instead of doing:

MyClass *instance = new MyClass();

you can do

shared_ptr<MyClass> instance(new MyClass());

shared pointers can track the number of shared pointers referencing the same object and free the memory automatically once all shared pointers to the same object go out of scope
0

Share this post


Link to post
Share on other sites
[quote name='CryZe' timestamp='1312768837' post='4846010']
[quote name='Wooh' timestamp='1312762339' post='4845970']
Using pointers is more work, more code and increased risk for mistakes so I always avoid pointers unless there is a good reason to use pointers.
[/quote]

If you aren't using pointers the object itself is getting saved on the stack. So you should sometimes use pointers. This way only the pointer variable itself is located on the stack and the object is located on the heap. You should only do this if you really need to, as dealing with pointers is a pain in the butt, and seeing as you're a beginner, there probably isn't a lot of need to do that.
[/quote]
Fixed that for you.
0

Share this post


Link to post
Share on other sites
[quote name='SymLinked' timestamp='1312783746' post='4846070']
[quote name='CryZe' timestamp='1312768837' post='4846010']
[quote name='Wooh' timestamp='1312762339' post='4845970']
Using pointers is more work, more code and increased risk for mistakes so I always avoid pointers unless there is a good reason to use pointers.
[/quote]

If you aren't using pointers the object itself is getting saved on the stack. So you should always use pointers. This way only the pointer variable itself is located on the stack and the object is located on the heap. That's it.
[/quote]

That's not true. If the variable is declared inside a heap-allocated class instance as a non-pointer, it will still be allocated on the heap. If you're inside function scope then sure, the variable will be allocated on the stack. Recommending someone to always use pointers is quite a blanket statement however.
[/quote]

Next time I shouldn't try to write my posts in like 10 seconds. I already knew all that stuff, and yes you shouldn't always allocate all of your objects on the heap. Sorry for the misunderstanding... I thought, that he as a beginner should just allocate all of them on the heap, so that he doesn't get problems like for example stack overflows. I simply should've said that. >.<
-1

Share this post


Link to post
Share on other sites
[quote]
I thought, that he as a beginner should just allocate all of them on the heap, so that he doesn't get problems like for example stack overflows. I simply should've said that
[/quote]
Even still, no.

Stack overflow is a rare problem, mostly caused by excessive recursion or placing large arrays on the stack (or objects that contain large arrays). It is also generally easy to fix.

Allocating data on the heap can lead to lots of common problems, including memory leaks and bad pointers. These problems can be difficult to track down and fix. It also is a bad idea to do dynamic allocation when it is unnecessary from a performance standpoint, because each allocation/deallocation involves traversing some data structure. Stack allocation is virtually free in comparison.
2

Share this post


Link to post
Share on other sites
Thanks for all the info. For some reason I had got into the habit of only using pointers but I think I will stop from now on. I have in the past had problems with memory leaks which is a pain.
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