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

Pointer to an abstract class

6 posts in this topic

#include "..\Objects\Objects.h"



class Idle;



class Activity

{

public:

    Objects *Actor;

    Goods *Target;

 

Objects and Goods are both abstract.

How can I declare an abstract object inside another class?

Thanks

Jack

Edited by lucky6969b
0

Share this post


Link to post
Share on other sites
[code=auto:0]
class a
{
public:
class b
{
public:
virtual void something() = 0;
}
}
[\code]

Not sure why you would want to do this.
0

Share this post


Link to post
Share on other sites

You want to do that to make that class only accessible form that class usually, this is what a PIMPL implementation often uses, you should avoid pimpl it's a bad pattern. You shouldn't be hiding the data a class is operating on.

 

You can instantiate a pointer to an abstract class by newing an object instance of a derived class on it.

 

class base:
{
    virtual void abstractMethod() = 0;
}
 
class derived : public base
{
    virtual void abstractMethod()
    {
         cout << "fubar" << endl;
    }
}
void main()
{
    Base* derivedInstance = new derived();
    derivedInstance->abstractMethod();
    delete derived;
}
0

Share this post


Link to post
Share on other sites

How can I declare an abstract object inside another class?

I'm not sure what you're trying to ask here.  Do you mean how do you instantiate objects of a concrete class derived from an abstract class?  Google for 'factory function'.

0

Share this post


Link to post
Share on other sites

You cannot produce an 'abstract object' at all, abstract classes are used for inheritance, as interface for a concrete class derived from it.

If Object and Goods are in fact not abstract, just use 'Target = new Goods()' and 'Actor = new Objects()' into the constructor or something if thats what you want (although I would probably just use static objects by deleting the asterisk if thats your plan).

0

Share this post


Link to post
Share on other sites

You want to do that to make that class only accessible form that class usually, this is what a PIMPL implementation often uses, you should avoid pimpl it's a bad pattern. You shouldn't be hiding the data a class is operating on.


Not trying to derail the topic (sorry), but I'd like to hear more about your reasoning for this statement (the parts I've emphasized).

IMO there's nothing inherently wrong about the PIMPL pattern (except that it produces a lot of boiler plate code - but at the same time it enables nice things like implicit sharing and reducing compile times).
Besides, declaring the data class inside the actual class would not really be the PIMPL pattern, as the PIMPL would still be "public" (not in the language kind of way, but in the "I see what you did there" kind of way) in C++ as it could be seen in the header (you'd usually have a private header that's only included in the implementation not in the declaration; also, only when used like that, the PIMPL pattern can reduce compile time, which is one of its main merrits).
[EDIT - _very_ exaggerated, to be honest]: Actually, isn't PIMP the only true object orientated pattern? Afterall, one of the main points is encapsulation. What's more encapsulated than only showing the actual interface to the user? The user should not care "how" and "what data", but only "what can I do with it?".

Back to the topic: to me the question is lacking some information. What are you trying to accomplish? To me it seems like you are actually asking how to instanciate objects of the "Objects" and "Goods" classes (btw, get rid of the plural form)!? If that is the case, you will need actual implementation of the abstract classes. This is a long shot, though, since some information is missing here. Edited by brx
1

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