source: doc/proposals/concurrency/notes/lit-review.md @ bf70aa9

ADTaaron-thesisarm-ehast-experimentalcleanup-dtorsdeferred_resndemanglerenumforall-pointer-decayjacob/cs343-translationjenkins-sandboxnew-astnew-ast-unique-exprnew-envno_listpersistent-indexerpthread-emulationqualifiedEnumresolv-newwith_gc
Last change on this file since bf70aa9 was db0fa7c, checked in by Thierry Delisle <tdelisle@…>, 7 years ago

Moved files and did some cleanup in the directories

  • Property mode set to 100644
File size: 702 bytes
Line 
1lit review :
2
3Lister77 : nested monitor calls
4        - explains the problem
5        - no solution
6        - Lister : An implementation of monitors.
7        - Lister : Hierarchical monitors.
8
9Haddon77 : Nested monitor calls
10        - monitors should be release before acquiring a new one.
11
12Horst Wettstein : The problem of nested monitor calls revisited
13        - Solves nested monitor by allowing barging
14
15David L. Parnas : The non problem of nesied monitor calls
16        - not an actual problem in real life
17
18M. Joseph and VoR. Prasad : More on nested monitor call
19        - WTF... don't use monitors, use pure classes instead, whatever that is
20
21Joseph et al, 1978).
22
23Toby bloom : Evaluating Synchronization Mechanisms
24        - Methods to evaluate concurrency
25
Note: See TracBrowser for help on using the repository browser.