#48 calling mocked methods is not thread-safe

[Kosta]

Similar to issue #47 calling mocked methods from different threads is not thread-safe; all the book-keeping need to be protected by a mutex (e.g., the calling counters go easily out-of-sync). I would like to add this simple patch to fix this behavior: https://github.com/AIM360/turtle/commit/1267fe714af5139eb698286be0d9c2c395ba16b6

[Mathieu Champlon]

Hi Kosta and sorry for the delay.

This is currently under work and although I was hoping to be able to avoid recursive mutexes, this is likely the easiest solution indeed.

Cheers,
MAT.

[Mathieu Champlon]

Thread safety has been introduced in http://sourceforge.net/p/turtle/code/730/
In order to activate the feature the symbol MOCK_THREAD_SAFE must be defined before including the library.

Does this meet your expectations?
I'll make a new release shortly but in the meanwhile any feedback will be greatly appreciated!

Thanks,
MAT.