Skip to content
Snippets Groups Projects
  1. May 04, 2010
  2. May 01, 2010
  3. Apr 30, 2010
  4. Apr 29, 2010
  5. Apr 28, 2010
  6. Apr 29, 2010
    • Monroe Linden's avatar
      Incorporate suggestions from Richard's review of the LLPlugin changes. · 77b13dc2
      Monroe Linden authored
      Use LLMutexLock (stack-based locker/unlocker) for the straightforward cases instead of explicit lock()/unlock().
      
      There are still a couple of cases (one overlapping lock lifetime and two loops that unlock the mutex to call another function inside the loop) where I'm leaving explicit lock/unlock calls.
      
      Rename LLPluginProcessParent::sPollThread to sReadThread, for consistency.
      
      Made the LLPluginProcessParent destructor hold mIncomingQueueMutex while removing the instance from the global list -- this should prevent a possible race condition in LLPluginProcessParent::poll().
      
      Removed a redundant check when calling LLPluginProcessParent::setUseReadThread().
      77b13dc2
  7. Apr 28, 2010
Loading