Re: [boost] Workaround for a msvc 7.1 & 8.0 bug surfaced in the boost 1.35 release part II

Hi Peter.

I renamed the local CRITICAL_SECTION to critical_section to avoid this ambiguity. See revision 45545.

Could you also add the comment from the original patch to explain why this has been done? Since there are no tests prepared that would catch this if it ever regressed... Best regards, Jurko Gospodnetić