> > I believe there's standard functions for allocating things like BSTR's > from the COM days (SysAllocString/SysFreeString) where the callee allocates > and the caller is responsible for deallocation but passing out raw wchar_t > pointers without agreeing on a deallocation method isnt great. >
I think you're heading in the right direction here. I suspect that passing a whcar_t* back from a function is too low-level and clumsy. I'm betting that someone has thought of this before and there is a technique I can't remember. There are probably classes (like BSTR) and functions for this, but what are they?! Web searches continue, but I'm not sure what to search for -- *GK*
