1. 09 Oct, 2012 1 commit
    • Michal 'vorner' Vaner's avatar
      [2292] Clarify test · d78dd497
      Michal 'vorner' Vaner authored
      And make it slightly stronger (it now checks something that should be
      mostly obvious too, but who knows, with software).
      d78dd497
  2. 08 Oct, 2012 1 commit
  3. 07 Oct, 2012 1 commit
  4. 21 Sep, 2012 1 commit
  5. 19 Sep, 2012 3 commits
  6. 17 Sep, 2012 1 commit
  7. 16 Sep, 2012 5 commits
  8. 11 Sep, 2012 1 commit
    • Mukund Sivaraman's avatar
      [2150] Allow DomainTree::find() to start at a lower level · 3c03d322
      Mukund Sivaraman authored
      Note that if a previous find() results in a PARTIALMATCH, the next
      find() (when passed a populated node chain and a non-absolute label
      sequence) starts at the down-node of the partial match's top of chain
      (deepest matched node).  The caller must pass the correctly formed
      non-absolute label sequence for that sub-tree-of-tree.
      3c03d322
  9. 29 Aug, 2012 3 commits
  10. 28 Aug, 2012 1 commit
  11. 21 Aug, 2012 1 commit
    • JINMEI Tatuya's avatar
      [2107] revised tree-data deleter mechanism: we now pass deleter to destroy. · 6679f424
      JINMEI Tatuya authored
      ...instead of give its type as a class template parameter and instantiate
      it within the tree.  it won't work (well) for ZoneData, because we need
      to know the RR class to delete RdataSet (which is the data type for
      ZoneData tree), but there's no way to tell the RR class about it.
      A good side effect of this change is that we now don't have to link
      the memory segment for the tree and its nodes with the zone data
      (although in practice it's quite likely to use the same segment for
      all of them).
      
      I also updated setData() (further from #2100); it now doesn't even delete
      any existing data.  This is partly relaetd to the above change on
      deleter - we cannot instantiate the deleter within this method.  We could
      pass the deleter as a parameter, but, actually, in the case of ZoneData
      we wouldn't have to delete the data; when setData() encounters existing
      data, it's more likely that ZoneData tries to extend the RdataSet list.
      It makes more sense to let ZoneData manage all data, including when to
      delete them.
      
      (although not absolutely necessary) I also changed the type of deleter
      in the domain tree test to highlight we could use a plain old function
      instead of a functor object.
      
      change size is big, but most of the changes are trivial conversion
      from something like <T, DT> to <T>.
      6679f424
  12. 03 Aug, 2012 1 commit
  13. 02 Aug, 2012 1 commit
  14. 31 Jul, 2012 3 commits
  15. 30 Jul, 2012 6 commits
  16. 27 Jul, 2012 2 commits
  17. 26 Jul, 2012 1 commit
  18. 25 Jul, 2012 1 commit
  19. 24 Jul, 2012 6 commits