Peter Fitzsimmons wrote in a message to Alan Clifford:

 PF> DosEnterCritSec() is a bad practice,  it is NEVER _required_
 PF> (you can always use a sem instead),  and shoots SMP OS/2 in
 PF> the foot.

In my opinion, DosEnterCritSec() is appropriate where you do not have full
control of the source code.  If you are writing a library, you can always
require as part of your API that the client check your internal semaphore
by calling a function provided for that purpose, but there are some cases
where this is not practical.  Many C language run-time libraries must stop
all threads in the process at some point, often inside low-level routines
such as malloc().  There really are things which are critical sections, and
declaring them as such is a good idea.
 
-- Mike


---