1. 24 May, 2008 9 commits
  2. 23 May, 2008 1 commit
  3. 22 May, 2008 4 commits
  4. 16 May, 2008 1 commit
    • Rémi Denis-Courmont's avatar
      Hide i_children and pp_children away · 8dba8057
      Rémi Denis-Courmont authored
      They can only be read safely under the Big Structure Lock in
      src/misc/objects.c, so it makes no sense for them to be public.
      
      By the way, making i_children volatile wouldn't magically solve
      thread-safety issues. The only correct use of volatile is in dealing
      with asynchronous changes _within_ the same thread, such as signal
      handling.
      
      P.S.: I wish modules were not objects, and I wonder why they are
      (they don't don't use threads, nor plugins, nor variables)
      8dba8057
  5. 08 May, 2008 5 commits
  6. 07 May, 2008 1 commit
  7. 04 May, 2008 2 commits
  8. 03 May, 2008 3 commits
  9. 02 May, 2008 1 commit
  10. 01 May, 2008 13 commits