TIP: Click on subject to list as thread! ANSI
echo: os2prog
to: Mike Bilow
from: Jonathan de Boyne Pollard
date: 1996-03-27 09:54:04
subject: Threads

MB>
  > In my opinion, DosEnterCritSec() is appropriate where [...]
  >                         Many C language run-time libraries
  > must stop all threads in the process at some point, often
  > inside low-level routines such as malloc().
MB>

  If the C runtime uses DosEnterCritSec to protect its heap, then send it
  back to the manufacturer!  There is *no* reason to stop processing a
  thread that is doing something totally unrelated to the heap if another
  thread calls malloc().

  Even Borland C++ for OS/2 uses semaphores for heap management.

  I'm with Peter.  There are almost *no* situations where use of
  DosEnterCritSec is justified.

  > JdeBP <
___
 X MegaMail 2.10 #0:

--- Maximus/2 3.01
* Origin: DoNoR/2,Woking UK (44-1483-725167) (2:440/4)
SEEN-BY: 50/99 78/0 270/101 620/243 711/401 409 410 413 430 808 809 934 955
SEEN-BY: 712/407 515 517 628 713/888 800/1 7877/2809
@PATH: 440/4 141/209 270/101 712/515 711/808 809 934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.