1. 10 Sep, 2009 1 commit
  2. 08 Sep, 2009 1 commit
  3. 04 Sep, 2009 1 commit
  4. 03 Sep, 2009 1 commit
  5. 02 Sep, 2009 1 commit
  6. 28 Aug, 2009 1 commit
  7. 19 Aug, 2009 1 commit
  8. 18 Aug, 2009 2 commits
  9. 04 Aug, 2009 1 commit
  10. 24 Jul, 2009 1 commit
  11. 23 Jul, 2009 1 commit
  12. 22 Jul, 2009 1 commit
  13. 15 Jul, 2009 1 commit
  14. 09 Jul, 2009 1 commit
  15. 01 Jul, 2009 1 commit
  16. 30 Jun, 2009 3 commits
  17. 29 Jun, 2009 1 commit
  18. 25 Jun, 2009 2 commits
  19. 18 Jun, 2009 1 commit
  20. 20 May, 2009 1 commit
  21. 19 May, 2009 1 commit
  22. 30 Apr, 2009 1 commit
  23. 28 Apr, 2009 1 commit
    • Mark Olesen's avatar
      minor build fix · 3ce125ff
      Mark Olesen authored
      - createBaffles used List::append(const T&), changed to DynamicList
      3ce125ff
  24. 24 Apr, 2009 1 commit
  25. 17 Apr, 2009 1 commit
  26. 02 Apr, 2009 1 commit
  27. 26 Mar, 2009 1 commit
    • mattijs's avatar
      sorted zones · 96da5f0e
      mattijs authored
      	modified:   ../applications/utilities/mesh/manipulation/setsToZones/setsToZones.C
      	modified:   dynamicMesh/polyTopoChange/polyTopoChange/polyTopoChange.C
      96da5f0e
  28. 23 Mar, 2009 1 commit
  29. 12 Mar, 2009 2 commits
  30. 06 Mar, 2009 1 commit
  31. 24 Feb, 2009 1 commit
  32. 18 Feb, 2009 1 commit
    • Mark Olesen's avatar
      use while (runTime.loop() { .. } where possible in solvers · 4b60453c
      Mark Olesen authored
      - change system/controlDict to use functions {..} instead of functions (..);
        * This is internally more efficient
      - fixed formatting of system/controlDict functions entry
      
      - pedantic change: use 'return 0' instead of 'return(0)' in the applications,
        since return is a C/C++ keyword, not a function.
      4b60453c
  33. 17 Feb, 2009 1 commit
    • Mark Olesen's avatar
      change solvers, utilities, etc. to use while (..) time-looping idiom · c2256e51
      Mark Olesen authored
      - this (now deprecated) idiom:
            for (runTime++; !runTime.end(); runTime++) { ... }
        has a few problems:
          * stop-on-next-write will be off-by-one (ie, doesn't work)
          * function objects are not executed on exit with runTime.end()
        Fixing these problems is not really possible.
      
      - this idiom
            while (runTime.run())
            {
                runTime++;
                ...
            }
        works without the above problems.
      c2256e51
  34. 09 Feb, 2009 1 commit
  35. 06 Feb, 2009 1 commit