1. 03 Nov, 2019 1 commit
  2. 06 Apr, 2019 1 commit
  3. 04 Apr, 2019 1 commit
  4. 07 Jan, 2019 1 commit
  5. 06 Feb, 2019 1 commit
  6. 06 Nov, 2018 1 commit
  7. 19 Oct, 2018 2 commits
  8. 19 Dec, 2017 1 commit
  9. 17 May, 2018 1 commit
    • Mark Olesen's avatar
      ENH: avoid memory leaks for HashPtrTable, PtrMap insertion (issue #749) · 48d654cf
      Mark Olesen authored
      - disallow insert() of raw pointers, since a failed insertion
        (ie, entry already existed) results in an unmanaged pointer.
      
        Either insert using an autoPtr, or set() with raw pointers or autoPtr.
      
      - IOobjectList::add() now takes an autoPtr instead of an object reference
      
      - IOobjectList::remove() now returns an autoPtr instead of a raw pointer
      48d654cf
  10. 05 Nov, 2017 1 commit
  11. 25 Sep, 2016 1 commit
  12. 15 Jul, 2016 1 commit
  13. 30 Apr, 2016 1 commit
    • Henry Weller's avatar
      GeometricField: Renamed internalField() -> primitiveField() and... · 3c053c2f
      Henry Weller authored
      GeometricField: Renamed internalField() -> primitiveField() and dimensionedInternalField() -> internalField()
      
      These new names are more consistent and logical because:
      
      primitiveField():
      primitiveFieldRef():
          Provides low-level access to the Field<Type> (primitive field)
          without dimension or mesh-consistency checking.  This should only be
          used in the low-level functions where dimensional consistency is
          ensured by careful programming and computational efficiency is
          paramount.
      
      internalField():
      internalFieldRef():
          Provides access to the DimensionedField<Type, GeoMesh> of values on
          the internal mesh-type for which the GeometricField is defined and
          supports dimension and checking and mesh-consistency checking.
      3c053c2f
  14. 20 Feb, 2016 1 commit
    • Henry Weller's avatar
      Boundary conditions: Added extrapolatedCalculatedFvPatchField · 99a10ece
      Henry Weller authored
      To be used instead of zeroGradientFvPatchField for temporary fields for
      which zero-gradient extrapolation is use to evaluate the boundary field
      but avoiding fields derived from temporary field using field algebra
      inheriting the zeroGradient boundary condition by the reuse of the
      temporary field storage.
      
      zeroGradientFvPatchField should not be used as the default patch field
      for any temporary fields and should be avoided for non-temporary fields
      except where it is clearly appropriate;
      extrapolatedCalculatedFvPatchField and calculatedFvPatchField are
      generally more suitable defaults depending on the manner in which the
      boundary values are specified or evaluated.
      
      The entire OpenFOAM-dev code-base has been updated following the above
      recommendations.
      
      Henry G. Weller
      CFD Direct
      99a10ece
  15. 10 Jan, 2016 1 commit
  16. 11 Nov, 2015 1 commit
  17. 14 Aug, 2011 1 commit
  18. 06 Aug, 2011 1 commit
  19. 11 May, 2011 1 commit
  20. 19 Jan, 2011 1 commit
  21. 14 Jan, 2011 1 commit
  22. 07 Jan, 2011 1 commit
  23. 05 Jan, 2011 2 commits
  24. 28 Jul, 2010 1 commit
  25. 13 Apr, 2010 1 commit
  26. 12 Apr, 2010 1 commit
  27. 29 Mar, 2010 1 commit
  28. 17 Sep, 2009 1 commit
  29. 18 Aug, 2009 1 commit
  30. 04 Aug, 2009 1 commit
  31. 31 Dec, 2008 1 commit
  32. 16 Dec, 2008 1 commit
  33. 25 Jun, 2008 2 commits
  34. 15 Apr, 2008 1 commit