Quote:Original post by EDI
well it all depends in how you define a 'sprite'
as far as we are concerned, a sprite is a single object in the game world, a character an item, etc.
and any sprite has the ability to be animated or moved, etc.
a sprite need not have an image associated with them,
or a sprite can have it's drawing overriden to allow for a more complex system of images or effects to be performened (a derived sprite) for particles and such.
again, it's all in how you define 'sprite'
so i dont think it is as 'matter of fact' as you say =)
if you define a sprite as being, the actual image data for a game object,
then yes that image data should be 'shared' via is has-a type system.
however, we define a sprite as being, the game object itself, and our image data comes from an ImageSet object.
I think EDI summed it up nicely here. Unless there is an absolute definition for "sprite" somewhere (a game programmers dictionary?) it is going to depend on your own situation. If a sprite is defined as the image data then I think most people here agree it 'has-a' sprite and if a sprite is defined as an actual tangeable object then it is 'is-a' sprite. Luckily for us I don't think there really is a game programmers dictionary so our life is filled with mystery :).
