1. 07 May, 2017 2 commits
  2. 05 May, 2017 3 commits
  3. 04 May, 2017 11 commits
  4. 02 May, 2017 4 commits
  5. 01 May, 2017 7 commits
    • Mark OLESEN's avatar
      ENH: HashSet iterators operator* now return Key. · f8c58bdd
      Mark OLESEN authored
      - much more useful than returning nil. Can now use with a for range:
          for (auto i : myLabelHashSet)
    • Mark OLESEN's avatar
      ENH: add HashTable::writeKeys and HashSet::writeList · 8f75bfbe
      Mark OLESEN authored
      - can use the hash-set writeList in combination with FlatOutput:
        Eg, flatOutput(myHashSet);
    • Mark OLESEN's avatar
      ENH: improve overall consistency of the HashTable and its iterators · c0a50dc6
      Mark OLESEN authored
      - previously had a mismash of const/non-const attributes on iterators
        that were confused with the attributes of the object being accessed.
      - use the iterator keys() and object() methods consistently for all
        internal access of the HashTable iterators. This makes the intention
        clearer, the code easier to maintain, and protects against any
        possible changes in the definition of the operators.
      - 'operator*': The standard form expected by STL libraries.
        However, for the std::map, this dereferences to a <key,value> pair,
        whereas OpenFOAM dereferences simply to <value>.
      - 'operator()': OpenFOAM treats this like the 'operator*'
      - adjusted the values of end() and cend() to reinterpret from nullObject
        instead of returning a static iteratorEnd() object.
        This means that C++ templates can now correctly deduce and match
        the return types from begin() and end() consistently.
        So that range-based now works.
            HashTable<label> table1 = ...;
            for (auto i : table1)
                Info<< i << endl;
        Since the 'operator*' returns hash table values, this prints all the
        values in the table.
    • Mark OLESEN's avatar
      ENH: ensure nullObject is large enough for reinterpret · 0298c02b
      Mark OLESEN authored
      - previously occupied 1 byte. Now occupies enough to hold a pointer,
        which helps if using reinterpret_cast to something that has some
        member content.
    • Mark OLESEN's avatar
      BUG: comparison to static end() for hashtable lookup. · 7cceda62
      Mark OLESEN authored
      - just use the iterator method found() as an alternative and
        convenient way to avoid the issue with less typing.
    • Mark OLESEN's avatar
      BUG: comparison with incorrect construction tables · dc57c016
      Mark OLESEN authored
      - previously hidden when hashtable used a static method and a
        different class for end()
    • Mark OLESEN's avatar
      ENH: support UList[labelRange] and SubList construction with labelRange · 805b76d4
      Mark OLESEN authored
      This uses a concept similar to what std::valarray and std::slice do.
      A labelRange provides a convenient container for holding start/size
      and lends itself to addressing 'sliced' views of lists.
      For safety, the operations and constructors restricts the given input range
      to a valid addressible region of the underlying list, while the labelRange
      itself precludes negative sizes.
      The SubList version is useful for patches or other things that have a
      SubList as its parameter. Otherwise the UList [] operator will be the
      more natural solution. The slices can be done with a labelRange, or
      a {start,size} pair.
           labelList list1 = identity(20);
           list1[labelRange(18,10)]  = -1;
           list1[{-20,25}] = -2;
           list1[{1000,5}] = -3;
           const labelList list2 = identity(20);
           list2[{5,10}] = -3;  // ERROR: cannot assign to const!
  6. 30 Apr, 2017 3 commits
  7. 29 Apr, 2017 5 commits
    • Mark OLESEN's avatar
      ENH: add some standard templates and macros into stdFoam.H · c65e2e58
      Mark OLESEN authored
      - some functionality similar to what the standary library <iterator>
        * stdFoam::begin() and stdFoam::end() do type deduction,
          which means that many cases it is possible to manage these types
          of changes.
          For example, when managing a number of indices:
             Map<labelHashSet> lookup;
          1) Longhand:
                  Map<labelHashSet>::const_iterator iter = lookup.begin();
                  iter != lookup.end();
              { .... }
          1b) The same, but wrapped via a macro:
              forAllConstIter(Map<labelHashSet>, lookup, iter)
              { .... }
          2) Using stdFoam begin/end templates directly
                  auto iter = stdFoam::begin(lookup);
                  iter != stdFoam::end(lookup);
              { .... }
          2b) The same, but wrapped via a macro:
              forAllConstIters(lookup, iter)
              { .... }
      Note that in many cases it is possible to simply use a range-based for.
           labelList myList;
           for (auto val : myList)
           { ... }
           for (const auto& val : myList)
           { ... }
      These however will not work with any of the OpenFOAM hash-tables,
      since the standard C++ concept of an iterator would return a key,value
      pair when deferencing the *iter.
      The deduction methods also exhibits some slightly odd behaviour with
      some PtrLists (needs some more investigation).
    • Mark OLESEN's avatar
      ENH: improve HashSet construction and assignment · 6a5ea9a2
      Mark OLESEN authored
      - make construct from UList explicit and provide corresponding
        assignment operator.
      - add construct,insert,set,assignment from FixedList.
        This is convenient when dealing with things like edges or triFaces.
    • Mark OLESEN's avatar
      ENH: support HashTable erasure via a FixedList · a2ddf7dd
      Mark OLESEN authored
      - propagate common erasure methods as HashSet::unset() method,
        for symmetry with HashSet::set()
    • Mark OLESEN's avatar
      STYLE: HashTable documentation · ded105c5
      Mark OLESEN authored
      - explicitly mention the value-initialized status for the operator().
        This means that the following code will properly use an initialized
            HashTable<label> regionCount;
            if (...)
            ... and also this;
            if (regionCount("something") > 0)
        Note that the OpenFOAM HashTable uses operator[] to provide read and
        write access to *existing* entries and will provoke a FatalError if
        the entry does not exist.
        The operator() provides write access to *existing* entries or will
        create the new entry as required.
        The STL hashes use operator[] for this purpose.
    • Mark OLESEN's avatar
      ENH: further refinement to edge methods · 1d9b311b
      Mark OLESEN authored
      - more hash-like methods.
        Eg, insert/erase via lists, clear(), empty(),...
      - minVertex(), maxVertex() to return the smallest/largest label used
      - improved documentation, more clarification about where/how negative
        point labels are treated.
  8. 28 Apr, 2017 4 commits
  9. 27 Apr, 2017 1 commit