Proposal: addition of thin RAII wrappers for ease of use

[amtopel]

Would you consider adding a header with some thin RAII wrappers to make using this library slightly easier? Here are a couple examples of what I'm thinking about:

class CPropValuePtr
{
public:
	CPropValuePtr() :
		m_p(NULL)
	{
	}

	~CPropValuePtr()
	{
		Free();
	}

	LPSPropValue* operator&() noexcept
	{
		return &m_p;
	}

	LPSPropValue operator->() noexcept
	{
		return m_p;
	}

	void Free() noexcept
	{
		MAPIFreeBuffer(m_p);
		m_p = NULL;
	}

	LPSPropValue m_p;
};


class CRowSetPtr
{
public:
	CRowSetPtr() :
		m_p(NULL)
	{
	}

	~CRowSetPtr()
	{
		Free();
	}

	LPSRowSet* operator&() noexcept
	{
		return &m_p;
	}

	LPSRowSet operator->() noexcept
	{
		return m_p;
	}

	void Free() noexcept
	{
		FreeProws(m_p);
		m_p = NULL;
	}

	LPSRowSet m_p;
};

[stephenegriffin]

Given the nuances of memory allocations in MAPI, this seems more likely to cause problems than to solve them. Best to leave these sorts of wrappers to projects that are actually using MAPI.

I'll just give an example: MAPI allocations are chained, so if you happened to get CRowSetPtr there and then also CPropValuePtr to a property in one of those rows, then you're going to either crash or leak memory depending on which one goes out of scope first.