Christian Costa wrote:
In that case our InitializeCriticalSection macro would have one more parameter (the name) than the real function.
Nope. It wouldn't. We would construct the name from __FILE__ and __LINE__.
It would have the filename and line number as the name... that would be enough to let you distinguish between locks. ... The chief advantage, though, is that it gets us automatically generated names with no source changes, at least for static calls...
In this case, CRITICAL_SECTION_INIT should be update, at least to have the line number. :-)
So, if everyone agree. That 's fine for me. :-) Would you submit a patch that handle that ?
I will give it a try. Then people can pass judgement on whether it's a good idea. - Dan