Re: mamaMsg_freeString issue

Les Spiro

I think the behaviour makes sense given the performance constraints we all
operate under. I think it would be useful to extend the programmers guide
and also state that (given a static string buffer) calls to this function
can also have unexpected results if multiple threads are working with the
same message object.

I donĀ¹t think this should be a problem in normal use cases.


On 13/11/2013 17:43, "Frank Quinn" <fquinn@...> wrote:

In summary, if the MAMA application developer calls a mamaMsg call to get
a pointer value, it should assume that the next MAMA call is perfectly
permitted to overwrite the buffer which that pointer is pointing to.

Join to automatically receive all group messages.