1. 23 May, 2017 1 commit
  2. 18 May, 2017 1 commit
  3. 17 May, 2017 1 commit
  4. 15 May, 2017 1 commit
  5. 28 Apr, 2017 1 commit
  6. 18 Apr, 2017 1 commit
  7. 13 Apr, 2017 2 commits
  8. 22 Mar, 2017 1 commit
  9. 21 Mar, 2017 1 commit
  10. 20 Mar, 2017 1 commit
  11. 16 Mar, 2017 1 commit
  12. 13 Feb, 2017 1 commit
  13. 09 Feb, 2017 8 commits
  14. 26 Jan, 2017 1 commit
  15. 18 Jan, 2017 1 commit
    • Thomas Guillem's avatar
      vout: remove vout_Reset() · 95810fbd
      Thomas Guillem authored
      Pictures from leaking decoders won't be reset anymore. This may cause a freeze
      if a vout is reused after a leaking decoder.
      
      The call to ThreadFlush(vout, true, INT64_MAX) is now done from ThreadReinit().
      95810fbd
  16. 09 Nov, 2016 1 commit
  17. 05 Nov, 2016 1 commit
  18. 10 Oct, 2016 1 commit
  19. 26 Sep, 2016 3 commits
  20. 23 Sep, 2016 2 commits
  21. 22 Sep, 2016 1 commit
  22. 28 Jul, 2016 5 commits
  23. 09 Jun, 2016 1 commit
    • Filip Roséen's avatar
      input/decoder: return-statement with expression is ill-formed · 8a052fe3
      Filip Roséen authored
      Having written too much C++ in my days, I wrongfully assumed that it
      was legal to have a return-statement with an expression in a function
      returning void, as long as the expression would yield void, in C (as
      it is in C++).
      
      However, according to the C99 ISO Standard (section 6.8.6.4p1) this is
      not the case.
      
      > [ :: 6.8.6.4p1 :: ]
      >
      > A return statement with an expression shall not appear in a function
      > whose return type is void. A return statement without an expression
      > shall only appear in a function whose return type is void.
      Signed-off-by: Rémi Denis-Courmont's avatarRémi Denis-Courmont <remi@remlab.net>
      8a052fe3
  24. 28 May, 2016 1 commit
  25. 24 May, 2016 1 commit