When Not to Create a Thread
So far, I’ve been singing the praises of multithreaded applications. Although there are a lot of great things about multithreaded applications, there are also some not-so-nice things. Some developers believe that the way to solve any problem is to divide it into threads. They could not be more wrong!
Threads are incredibly useful and have a place, but when you use threads you can create new problems while trying to solve the old ones. For example, let’s say you’re developing a word processing application and want to allow the printing function to run as its own thread. This sounds like a good idea because the user can immediately go back and start editing the document while it’s printing. But wait—this means that the ...
Get Windows® via C/C++, Fifth Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
