Re: STL removal algorithm question

Old Wolf wrote:


Let me add that this is only if you decide to stick with the
idea of using a vector of structs of BSTR. My preferred
solution is to work with structs of CComBSTR, or
some other string type; and then generate a struct of BSTR
only when it's needed for a COM interface call; it makes
all of this management crap unnecessary.


Something like this:

struct BstrManager
{
    ~BstrManager() { clear(); }
    void clear()
    {
      for_each(all.begin(), all.end(), SysFreeString);
      all.clear();
    }
    BSTR createString(wchar_t const *s, size_t len)
    {
      BSTR b = SysAllocStringLen(s, len);
      all.push_back(b);
      return b;
    }
    BSTR copyString( BSTR s )
    {
      BSTR b = SysAllocString(s);
      all.push_back(b);
      return b;
    }
    void deleteString( BSTR b )
    {
      std::vector<BSTR>::iterator it = all.find(b);
        if ( it != all.end() ) { SysFreeString(b); all.erase(it); }
    }

  private:
    std::vector<BSTR> all;
};

Then in your code you can go:
  MyStruct m;
  m.somestring = manager.createString(L"Hello", 5);
  m.otherstring = manager.copyString(m.somestring);
  vec.push_back(m);
// ......
  vec.clear();
  manager.clear();