EDIT:

Here's the improved version:

#include <SFML/Graphics.hpp>
#include <memory>
#include <map>


enum SpriteId
{
    ITEM1,
    ITEM2,
    ITEM3,
    ITEM4,
    ITEM5
};

const int WIDTH = 100;
const int HEIGHT = 100;

typedef std::tr1::shared_ptr< sf::Sprite > SpritePtr;
typedef std::map< SpriteId, SpritePtr > SpriteMap;
typedef std::map< SpriteId, SpritePtr >::iterator iter;

class SpriteManager
{
private:
    SpriteMap spriteMap;
    sf::Texture& m_texture;
    void clipSprite(SpriteId name)
    {
        spriteMap.at(name)->setTexture(m_texture);
        switch(name)
        {
        case ITEM1: spriteMap.at(name)->setTextureRect(sf::IntRect(0,0,WIDTH,HEIGHT));break;
        case ITEM2: spriteMap.at(name)->setTextureRect(sf::IntRect((1*WIDTH),0,WIDTH,HEIGHT));break;
        case ITEM3: spriteMap.at(name)->setTextureRect(sf::IntRect((2*WIDTH),0,WIDTH,HEIGHT));break;
        case ITEM4: spriteMap.at(name)->setTextureRect(sf::IntRect((3*WIDTH),0,WIDTH,HEIGHT));break;
        case ITEM5: spriteMap.at(name)->setTextureRect(sf::IntRect((4*WIDTH),0,WIDTH,HEIGHT));break;
        //default: should i create a special "Error" sprite and load it, akin to Valve's ERROR models?
        //         or maybe create and throw an exception.
        }
    }
public:
    SpriteManager(sf::Texture& texture) : m_texture(texture)
    {}
    SpritePtr getSprite(SpriteId name)
    {
        if(!spriteMap[name])
        {
            spriteMap[name] = std::tr1::make_shared< sf::Sprite >();
            clipSprite(name);
            return spriteMap[name];
        }
        else
            return spriteMap[name];

    }
    // I can call reset for each pointer to force them to deallocate, 
    // but that would just be replicating the initial raw pointer problem
    // I don't really need a destructor here, right?
    //~SpriteManager()
    //{
    //  for(iter i = spriteMap.begin(); i != spriteMap.end(); ++i )
    //  {
    //      i->second.reset();
    //  }
    //}
};

int main()
{
    sf::RenderWindow window(sf::VideoMode(800,600), "Test", sf::Style::Titlebar | sf::Style::Close);

    sf::RectangleShape background(sf::Vector2f(800.0f,600.0f));

    window.setFramerateLimit(30);

    sf::Texture spriteSheet;

    if(!spriteSheet.loadFromFile("SpriteSheet.png"))
    {
        return 1;
    }

    SpriteManager sprites(spriteSheet);

    SpritePtr sprite = sprites.getSprite(ITEM1);
    SpritePtr sprite2 = sprites.getSprite(ITEM2);

    sprite->setPosition(100,100);
    sprite2->setPosition(200,100);

    while(window.isOpen())
    {
        sf::Event event;
        while( window.pollEvent(event))
        {
        
            if(event.type == sf::Event::Closed)
            {
                window.close();
            }
        }

        window.clear();
        window.draw(background);
        window.draw(*sprite);
        window.draw(*sprite2);
        window.display();
    }

    return 0;
}

A thing to note here that this is just an example; it's a test model. That is why everything is in a single .cpp file and the item names are not descriptive.

I'm trying to make a sprite cache for SFML sprites. The basic idea i got was to use a map of an enum and a sprite pointer. Then when I would ask for a certain sprite I'd have a manager that would check if the pointer for that sprite is null. If it is, then it would create a new sprite object and clip it to fit what it's supposed to be. If it isn't null then it means that the sprite object for this particular enum already exists and i get that.

1. Is the destructor ok? I figured that since I'm allocating sprites that i should delete them all upon the manager going out of scope, though the more i think about it the more uneasy i feel.

2. What would i do if i have to have two of the same sprites on the screen at the same time? Basically what happens now is, if i have two calls for a sprite with the same name, for ex.:

I won't actually have two sprites on the screen but only one at the position 100x , 200y, since when I called the first getSprite I created a sprite under ITEM1 key and then when I call the getSprite method the second time I get that first sprite again. Now this is great for memory conservation, however a lot of the times I'll need to have multiple instances of the same sprite on screen. For that I have an idea to add some sort of a counter or something, but nothing concrete yet. Any suggestions? Nvm, I'm an idiot.

Also I wasn't sure if I should post this here or on StackOverflow, since this works but it isn't complete yet and I'm having some issues with it. If it's on the wrong site I'm sorry i goofed.

A thing to note here that this is just an example, a test model. That is why everything is in a single .cpp file and the item names are not descriptive.

I'm trying to make a sprite cache for SFML sprites. The basic idea I got was to use a map of an enum and a sprite pointer. Then when I would ask for a certain sprite I'd have a manager that would check if the pointer for that sprite is null. If it is, then it would create a new sprite object and clip it to fit what it's supposed to be. If it isn't null, then it means that the sprite object for this particular enum already exists, and I get that.

1. Is the destructor ok? I figured that since I'm allocating sprites that I should delete them all upon the manager going out of scope, though the more I think about it the more uneasy I feel.

2. What would I do if I have to have two of the same sprites on the screen at the same time? Basically what happens now is, if I have two calls for a sprite with the same name:

   sf::Sprite *sprite1 = sprites.getSprite(ITEM1);
   sprite1->setPosition(100,100);
   sf::Sprite *sprite2 = sprites.getSprite(ITEM1);
   sprite2->setPosition(100,200);
   

I won't actually have two sprites on the screen but only one at the position 100x, 200y, since when I called the first getSprite I created a sprite under ITEM1 key and then when I call the getSprite method the second time I get that first sprite again. Now this is great for memory conservation, however a lot of the times I'll need to have multiple instances of the same sprite on screen. For that I have an idea to add some sort of a counter or something, but nothing concrete yet. Any suggestions?

A thing to note here that this is just an example; it's a test model. That is why everything is in a single .cpp file and the item names are not descriptive.