multithreading

[Kragen Sitaker]

pinard at iro.umontreal.ca (François Pinard) writes:
> Using Queue also means creating client-server relationships for handling data
> movement.  In a threaded project, implemented queues are quite fundamental in
> the overall description of the project design and algorithms, but I would not
> overly multiply queues for each and every tiny aspect of data movement, when
> mere locks are sufficient.  Multiplying queues for everything and everywhere
> in a project might impair its overall legibility, drawning the fish.

I've been following this discussion with interest, but I'm afraid it's
a bit abstract for me.  I haven't written a lot of multithreaded
systems.  Can you give an example of a case where using a queue
instead of just a lock makes the code a lot more complicated?