Are array of pointers to different types possible in c++?

14,079

Solution 1

C++ is C with more stuff. So if you want to do it the C way, as above you just make an array of void pointers

void *ary[10];
ary[0] = new int();
ary[1] = new float();

DA.

If you want to do things the object oriented way, then you want to use a collection, and have all the things you going to be adding to the collection derive from the same base object class that can be added to the collection. In java this is "Object", C++ has no base object built in, but any collection library you use will have such a thing that you can subclass.

Solution 2

Usually if you want to have a collection of different "types" of pointers, you implement it in a way where they derive off a base class/interface and store a pointer to that base. Then through polymorphism you can have them behave as different types.

class Base
{
public:
    virtual void doSomething() = 0;
};

class A : public Base
{
    void doSomething() { cout << "A\n"; } 
};

class B : public Base
{
    void doSomething() { cout << "B\n"; } 
};

std::vector<Base*> pointers;
pointers.push_back(new A);
pointers.push_back(new B);

Solution 3

An array of pointers to void has already been mentioned. If you want to make it practical and useful, consider using an array (or, better, vector) of boost::any.

Solution 4

... if you use a void *, it's easy ;-)

Solution 5

Yes. Two ways:

• Pointers to a base class type, which point to objects of types derived from that base type.
• Untyped void * pointers, which must be cast manually to the actual object types they point to.

The first approach is standard object-oriented programming.

The second approach is useful for low-level programming (e.g., device drivers, memory management libraries, etc.), and is considered dangerous and suitable only for programmers who know exactly what they're doing. Obviously, it requires additional bookkeeping info to tell you what each pointer's real type is.

Share:
14,079
SomeUser
Author by

SomeUser

About me

Updated on July 30, 2022

Comments

  • SomeUser
    SomeUser almost 2 years

    Are array of pointers to different types possible in c++? with example please)

  • SomeUser
    SomeUser over 14 years
    can you give little example?))
  • CookieOfFortune
    CookieOfFortune over 14 years
    and lead to potentially explosive situations!
  • asveikau
    asveikau over 14 years
    char *c_string = "Hello World"; MyCPlusPlusClass *obj = new MyCPlusPlusClass(); void *SomeArray[] = {c_string, obj}; If course, you'd damn well better have a way of remembering what's what. :-)
  • asveikau
    asveikau over 14 years
    I like this answer. I would add that you can also query which type is which dynamically, using dynamic_cast... Though some would argue that's a bad thing. :-)
  • sbi
    sbi over 14 years
    Given what you showed, how in the world are you to find out what types those pointers actually point to?
  • sbi
    sbi over 14 years
    @asveikau: A dynamic_cast is, basically, a switch over types. And Switching over types is just a sign of (irrational) fear of polymorphism. When you're tempted to do that, use virtual functions instead.
  • stu
    stu over 14 years
    well, firstly, that wasn't the question, but to answer, there's all sorts of ways. 1) you can have a parallel array with the type encoded in it. 2) you can make the array elements structures of a type variable and a union with all the different kinds of things you might want to put in there. There's 2 just off the top of my head. I'm sure somebody else can come up with slicker alternatives.
  • kriss
    kriss about 14 years
    @sbi: and you can also use RTTI.
  • sbi
    sbi about 14 years
    @kriss: No, you can't. RTTI only works within polymorphic class hierarchies. Given a void*, the runtime system gives you nothing to find out what it points to.
  • kriss
    kriss about 14 years
    @sbi: you are right. If he want's to use RTTI the OP should put all his structures in a common class hierarchy, however the base class can still be quite empty. Well, that's not much better than using a union plus a discriminating enum type.
  • stu
    stu about 14 years
    in fact, it's basically the same thing. :-) Except there's more C++ gunky overhead. :-))