| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Threads |
Jonathan de Boyne Pollard wrote in a message to Mike Bilow: > 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(). JdBP> If the C runtime uses DosEnterCritSec to protect its heap, JdBP> then send it back to the manufacturer! There is *no* JdBP> reason to stop processing a thread that is doing something JdBP> totally unrelated to the heap if another thread calls JdBP> malloc(). I agree that semaphores may be a better approach in most instances, but I think that short critical sections may end up giving more robust code. JdBP> Even Borland C++ for OS/2 uses semaphores for heap JdBP> management. Borland actually has an extremely unusual heap management system. JdBP> I'm with Peter. There are almost *no* situations where JdBP> use of DosEnterCritSec is justified. I suppose I could agree on "almost no" situations. -- Mike ---* Origin: N1BEE BBS +1 401 944 8498 V.34/V.FC/V.32bis/HST16.8 (1:323/107) 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: 323/107 170/400 396/1 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™.