template <GLenum TextureT> class OGLTextureImpl
{
//generation, deletion and binding here

}
//

template <GLenum ProgramT> class OGLProgramImpl
{
//generation, deletion and binding here

}

template <GLenum TextureT, typename BaseT> OGLTextureImpl :
    public BaseT
{
   OGLTextureImpl() {glGenTextures(1, m_id);}
   ~OGLTextureImpl() {glDeleteTextures(1, m_id);}

   virtual void bind() {
      glBindTexture(TextureT, m_id)
   }
   private:
      GLuint m_id;
}

class Texture {
   //..

   virtual void bind()=0;
};

class Texture2D : public Texture {
//..

};

class OGLTexture2D : public OGLTextureImpl<GL_TEXTURE_2D, Texture2D>
{
// here other ogl 2d texture stuff

};

quote:

---

Original post by valoh
For the Object template I don't see a reason to use that. Where do you save code? All the code you save at the first view, you have to type for the policy class. Imo you can then better leave out the Object base class and only use the templates for classes with same creation and deletion but different GLenums.

---

quote:

---

Also an interesting trick with the "delegation to a sister class", but I probably would prefer a design without multiple/virtual inheritance.
As far as I know you have always a runtime overhead with virtual inheritance.

---

quote:

---

And for what do you need the GLTexture class?

---