1. 07 Aug, 2018 1 commit
    • luz.paz's avatar
      Misc. typos · 7f9b54a3
      luz.paz authored
      Found via `codespell -q 3`
      7f9b54a3
  2. 21 Jun, 2018 1 commit
  3. 05 Jun, 2018 1 commit
  4. 23 Feb, 2018 1 commit
  5. 11 Dec, 2017 1 commit
  6. 08 Nov, 2017 1 commit
    • Robert Maynard's avatar
      vtkm::ListForEach can handle passing any number of extra arguments · cc71e8ec
      Robert Maynard authored
      Rather than requiring all the arguments to be placed as member variables to
      the functor you can now pass extra arguments that will be added to the functor
      call signature.
      
      So for example:
      
        vtkm::ForEach(functor, vtkm::TypeListTagCommon(), double{42.0}, int{42});
      
      will be converted into:
      
        functor(vtkm::Int32, double, int)
        functor(vtkm::Int64, double, int)
        functor(vtkm::Float32, double, int)
        functor(vtkm::Float64, double, int)
        ...
      cc71e8ec
  7. 07 Nov, 2017 1 commit
  8. 20 Sep, 2017 1 commit
    • Kenneth Moreland's avatar
      Update copyright for Sandia · c3a3184d
      Kenneth Moreland authored
      Sandia National Laboratories recently changed management from the
      Sandia Corporation to the National Technology & Engineering Solutions
      of Sandia, LLC (NTESS). The copyright statements need to be updated
      accordingly.
      c3a3184d
  9. 30 Aug, 2017 1 commit
  10. 25 May, 2017 1 commit
  11. 30 Dec, 2016 1 commit
  12. 29 Dec, 2016 1 commit
  13. 16 Nov, 2016 1 commit
    • Kenneth Moreland's avatar
      Remove exports for header-only functions/methods · fdaccc22
      Kenneth Moreland authored
      Change the VTKM_CONT_EXPORT to VTKM_CONT. (Likewise for EXEC and
      EXEC_CONT.) Remove the inline from these macros so that they can be
      applied to everything, including implementations in a library.
      
      Because inline is not declared in these modifies, you have to add the
      keyword to functions and methods where the implementation is not inlined
      in the class.
      fdaccc22
  14. 23 Sep, 2016 2 commits
  15. 31 Aug, 2016 1 commit
  16. 15 Dec, 2015 1 commit
  17. 17 Sep, 2015 2 commits
    • Kenneth Moreland's avatar
      Declare new VTKM_STATIC_ASSERT · b15940c1
      Kenneth Moreland authored
      This is to be used in place of BOOST_STATIC_ASSERT so that we can
      control its implementation.
      
      The implementation is designed to fix the issue where the latest XCode
      clang compiler gives a warning about a unused typedefs when the boost
      static assert is used within a function. (This warning also happens when
      using the C++11 static_assert keyword.) You can suppress this warning
      with _Pragma commands, but _Pragma commands inside a block is not
      supported in GCC. The implementation of VTKM_STATIC_ASSERT handles all
      current cases.
      b15940c1
    • Kenneth Moreland's avatar
      Add third party wrappers around boost macros. · 2ff6576c
      Kenneth Moreland authored
      The boost assert macros seem to have an issue where they define an
      unused typedef. This is causing the XCode 7 compiler to issue a warning.
      Since the offending code is in a macro, the warning is identified with
      the VTK-m header even though the code is in boost. To get around this,
      wrap all uses of the boost assert that is causing the warning in the
      third party pre/post macros to disable the warning.
      2ff6576c
  18. 13 Aug, 2015 1 commit
  19. 30 Jul, 2015 1 commit
    • Kenneth Moreland's avatar
      Always disable conversion warnings when including boost header files · 21b3b318
      Kenneth Moreland authored
      On one of my compile platforms, GCC was giving conversion warnings from
      any boost include that was not wrapped in pragmas to disable conversion
      warnings. To make things easier and more robust, I created a pair of
      macros, VTKM_BOOST_PRE_INCLUDE and VTKM_BOOST_POST_INCLUDE, that should
      be wrapped around any #include of a boost header file.
      21b3b318
  20. 21 May, 2015 1 commit
  21. 22 Oct, 2014 2 commits
  22. 08 Oct, 2014 1 commit
    • Kenneth Moreland's avatar
      Allow longer base lists · b2298172
      Kenneth Moreland authored
      Previously we just hand coded base lists up to 4 entries, which was fine
      for what we were using it for. However, now that we want to support base
      types of different sizes, we are going to need much longer lists.
      b2298172
  23. 15 May, 2014 1 commit
    • Kenneth Moreland's avatar
      Add classes to manage point coordinates. · 7d769a8f
      Kenneth Moreland authored
      Each type of point coordinates has its own class with the name
      PointCoordinates*. Currently there is a PointCoordiantesArray that contains
      an ArrayHandle holding the point coordinates and a PointCoordinatesUniform
      that takes the standard extent, origin, and spacing for a uniform rectilinear
      grid and defines point coordiantes for that. Creating new PointCoordinates
      arrays is pretty easy, and we will almost definitely add more. For example,
      we should have an elevation version that takes uniform coordinates for
      a 2D grid and then an elevation in the third dimension. We can probably
      also use a basic composite point coordinates that can build them from
      other coordinates.
      
      There is also a DynamicPointCoordinates class that polymorphically stores
      an instance of a PointCoordinates class. It has a CastAndCall method that
      behaves like DynamicArrayHandle; it can call a functor with an array handle
      (possible implicit) that holds the point coordinates.
      7d769a8f
  24. 31 Mar, 2014 1 commit
    • Kenneth Moreland's avatar
      Add tag-based type list templates · c2d926fa
      Kenneth Moreland authored
      Provies a list of types in a template like boost::mpl::vector and a
      method to call a functor on each type. However, rather than explicitly
      list each type, uses tags to identify the list. This provides the
      following main advantages:
      
      1. Can use these type lists without creating horrendously long class
      names based on them, making compiler errors easier to read. For example,
      you would have a typename like MyClass<TypeListTagVectors> instead of
      MyClass<TypeList<Id3,Vector2,Vector3,Vector4> > (or worse if variadic
      templates are not supported). This is the main motivation for this
      implementation.
      
      2. Do not require variadic templates and usually few constructions. That
      should speed compile times.
      
      There is one main disadvantage to this approach: It is difficult to get
      a printed list of items in a list during an error. If necessary, it
      probably would not be too hard to make a template to convert a tag to a
      boost mpl vector.
      c2d926fa