1. 05 Jan, 2009 1 commit
    • Mark Olesen's avatar
      rename xfer<T> class to Xfer<T> · 19503c93
      Mark Olesen authored
      - The capitalization is consistent with most other template classes, but
        more importantly frees up xfer() for use as method name without needing
        special treatment to avoid ambiguities.
        It seems reasonable to have different names for transfer(...) and xfer()
        methods, since the transfer is occuring in different directions.
        The xfer() method can thus replace the recently introduced zero-parameter
        transfer() methods.
        Other name candidates (eg, yield, release, etc.) were deemed too abstract.
  2. 31 Dec, 2008 1 commit
  3. 12 Dec, 2008 1 commit
  4. 24 Oct, 2008 1 commit
    • Mark Olesen's avatar
      polyMesh, fvMesh xfer constructors · 23476071
      Mark Olesen authored
      - drop copy components constructors in favour of the xfer versions. Even if
        the caller sends through constant data, if will be automatically promoted
        to xfer (via a copy operation).
  5. 25 Jun, 2008 2 commits
  6. 15 Apr, 2008 1 commit