Header files & Template Class

I have made a simple template class:

Code:

---

template <typename T1>
class POSITIONAL
{
    public:
        POSITIONAL(T1 varOne, T1 varTwo);
        POSITIONAL();
        ~POSITIONAL();
        void operator= (POSITIONAL& rhs);
        T1 posX;
        T1 posY;
};


template <typename T1>
POSITIONAL<T1>::POSITIONAL(T1 varOne, T1 varTwo)
{
    posX = varOne;
    posY = varTwo;
};

template <typename T1>
POSITIONAL<T1>::POSITIONAL()
{
    posX = 0;
    posY = 0;
};

template <typename T1>
void POSITIONAL<T1>::operator= (POSITIONAL<T1>& rhs)
{
    posX = rhs.posX;
    posY = rhs.posY;
}

template <typename T1>
POSITIONAL<T1>::~POSITIONAL()
{
};

---

Ok, so I have a few questions.

1) Should each class allocate/de-allocate its own memory. If so, when the compiler sets aside memory for a class (containing one such as this, but say this allocates and the 2 variables are pointers), does it set aside further memory or does it know that this class will do it itself?

2) When you use this class within another class, don't you just need to #include it? Code:Blocks is giving me trouble in not recognizing classes within classes. Keeps telling me "error: 'POSITIONAL' is not a type.

Quote:

---

1) Should each class allocate/de-allocate its own memory. If so, when the compiler sets aside memory for a class (containing one such as this, but say this allocates and the 2 variables are pointers), does it set aside further memory or does it know that this class will do it itself?

---

My answer to one is yes. If a class allocates memory, it must deallocate it. Now you said pretend the two member data are pointers. In such a case, the size of the class is at least the size of two pointers, and the compiler will set aside memory for that. The pointers themselves point to the memory you allocate. The size of the memory you allocate has nothing to do with the memory that the compiler will set aside for your class to store it's data.

Quote:

---

2) When you use this class within another class, don't you just need to #include it? Code:Blocks is giving me trouble in not recognizing classes within classes. Keeps telling me "error: 'POSITIONAL' is not a type.

---

That's correct. POSITIONAL isn't a type, POSITIONAL<T> where T is some other complete type initializes POSITIONAL is a type.

Code:

---

SPRITE::SPRITE(int width, int height):GRAPHIC(width, height)
{
        POSITIONAL<int> * gfxVelocity = new POSITIONAL(0,0);
...
}

---

Here is an example of what I have, but it is not being recognized.

Quote:

---

The size of the memory you allocate has nothing to do with the memory that the compiler will set aside for your class to store it's data.

---

So I obviously have a SPRITE class that contains a POSITIONAL. When a SPRITE is initialized, does it set aside memory for a POSITIONAL (even if it handles its own allocation)? This is just a point I have stuck in my head, that memory is being set aside twice for a class within a class, and its murky enough in there.

It sets aside memory for a POSITIONAL<T>. If that is two pointers big, then the compiler sets aside memory for that.

The pointers will contain an address as a value, which is where the memory that you allocated is actually stored. Since this allocation happens at run-time, the memory you allocated does not contribute to the size of the class. Only the size of the pointers will contribute to the size of the class.

But it is important to note, that even if you want those two variables in the class we are talking about to be pointers for the sake of discussion, the fact is that they aren't. A pointer is, for example, T*.

As for the error about POSITIONAL not being recognized that is because you omitted this piece:

Code:

---

POSITIONAL<int> * gfxVelocity = new POSITIONAL<int>(0,0);

---

Put another way, POSITIONAL isn't a type but a template, that only becomes a type after the template is initialized. A separate class will be initialized with all the Ts defined as ints ... or doubles... etc.

Make sure you don't forget smart pointers: SourceForge.net: Raw pointer issues - cpwiki
And I should ask: is there even a need to create a new positional on the heap?
Btw, it's not good practice to use UPPERCASE names for types since they can clash with macros.