1. 07 Feb, 2010 1 commit
  2. 06 Feb, 2010 2 commits
  3. 05 Jan, 2010 1 commit
  4. 16 Oct, 2009 1 commit
  5. 09 Mar, 2009 1 commit
  6. 28 Feb, 2009 2 commits
  7. 14 Oct, 2008 1 commit
  8. 12 Oct, 2008 3 commits
  9. 20 Sep, 2008 1 commit
  10. 01 Sep, 2008 1 commit
  11. 13 Aug, 2008 1 commit
  12. 11 Aug, 2008 1 commit
  13. 06 Jul, 2008 4 commits
  14. 06 Jun, 2008 1 commit
  15. 26 May, 2008 2 commits
  16. 23 May, 2008 1 commit
  17. 10 May, 2008 2 commits
  18. 04 May, 2008 1 commit
  19. 01 May, 2008 1 commit
  20. 17 Apr, 2008 1 commit
    • Michael Ploujnikov's avatar
      fixed misc/stats.c:399: warning: comparison between signed and unsigned in... · 47240a15
      Michael Ploujnikov authored
      fixed misc/stats.c:399: warning: comparison between signed and unsigned in function '__stats_TimerClean'
      
      Based on usage of i_id, other stats_* functions and my opinion i_id should be unsigned int instead of int, but I might be missing the bigger picture related to changing public APIs. Please, let me know how to correctly deal with such warnings.
      47240a15
  21. 15 Apr, 2008 3 commits
  22. 14 Apr, 2008 1 commit
  23. 25 Mar, 2008 1 commit
  24. 09 Feb, 2008 1 commit
  25. 24 Jan, 2008 2 commits
  26. 12 Dec, 2007 1 commit
  27. 16 Feb, 2007 1 commit
  28. 22 Dec, 2006 1 commit
    • Clément Stenac's avatar
      Add facilities to report and enrich error messages. · 65d21833
      Clément Stenac authored
      The idea is that a given error should be reported only once to the user.
      At the moment, for example, we can get:
      - "no suitable access module" (printed by module_Need)
       - "unable to create access" (printed by input/access)
       - "unable to open stream" (printed by input/input)
       - ...
      
      The facilities provided here are:
      * msg_StackSet( code, message ) : "throw" a new error
      * msg_StackAdd( message ) : Append a message allowing to trace the message
      * msg_StackMsg() : Retrieve the message
      
      So, in the previous example, module_Need would msg_StackSet( code, "no
      suitable access module"), then input/input would add "unable to create
      access" and finally, input/input can print the "unable to open stream:
      unable to create access: no suitable module" message.
      
      The three functions are context-free, you don't need a vlc_object, so
      that we can add verbose error reporting everywhere.
      
      65d21833