- 12 Dec, 2013 1 commit
-
-
Vittorio Giovara authored
-
- 27 Oct, 2013 1 commit
-
-
Stefano Sabatini authored
-
- 07 Oct, 2013 1 commit
-
-
Niv Sardi authored
See http://en.wikipedia.org/wiki/Graphics_display_resolutionSigned-off-by: Niv Sardi <xaiki@evilgiggle.com> Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
-
- 11 Aug, 2013 1 commit
-
-
Michael Niedermayer authored
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 08 Mar, 2013 1 commit
-
-
Carl Eugen Hoyos authored
Fixes a fate failure with icc 13.1
-
- 07 Mar, 2013 1 commit
-
-
Reimar Döffinger authored
Make sure the behavior does not change with the locale. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 03 Mar, 2013 1 commit
-
-
Reimar Döffinger authored
As far as I can tell the code should not change behaviour depending on locale in any of these places. Signed-off-by: Reimar Döffinger <Reimar.Doeffinger@gmx.de>
-
- 22 Feb, 2013 1 commit
-
-
Senthilnathan M authored
Fix trac ticket #2258. Signed-off-by: Senthilnathan M <senthilnathan.maadasamy@gmail.com> Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
-
- 03 Feb, 2013 1 commit
-
-
Dave Rice authored
Signed-off-by: Stefano Sabatini <stefasab@gmail.com>
-
- 04 Dec, 2012 1 commit
-
-
Anton Khirnov authored
-
- 02 Dec, 2012 1 commit
-
-
Nicolas George authored
Allow to parse durations >= 24:00:00.
-
- 29 Oct, 2012 1 commit
-
-
Stefano Sabatini authored
Return an error in case the video size specifications contains spurious trailing chars, like in "320x240foobar".
-
- 22 Oct, 2012 1 commit
-
-
Stefano Sabatini authored
Fix warning.
-
- 20 Oct, 2012 1 commit
-
-
Stefano Sabatini authored
Avoid to divide num and den by gcd in case of a parsed expression, since that is already done in av_d2q(), and force reduction in case of "a:b" form, allowing to honour the max parameter. The latter change is consistent with the a/b case, and with the documentation.
-
- 11 Oct, 2012 2 commits
-
-
Mans Rullgard authored
The const qualifier is still removed although it happens inside the strtol() function so no warning is generated. Fixes: libavutil/parseutils.c:110:11: warning: assignment discards qualifiers from pointer target type Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Mans Rullgard authored
- make tables static const - remove useless use of compound literal - break long lines - fix a comma/semicolon typo Signed-off-by: Mans Rullgard <mans@mansr.com>
-
- 10 Oct, 2012 1 commit
-
-
Mans Rullgard authored
The error codes differ between systems so printing the value makes the fate test fail on some systems. Signed-off-by: Mans Rullgard <mans@mansr.com>
-
- 06 Oct, 2012 2 commits
-
-
Mans Rullgard authored
An alpha specifier outside the valid range results in a conversion from double to long with undefined result. Range-checking the double and only converting it after it passes avoids this. Fixes fate-parseutils errors on some systems. Signed-off-by: Mans Rullgard <mans@mansr.com>
-
Diego Biurrun authored
This guarantees stable output for comparing test results.
-
- 17 Sep, 2012 2 commits
-
-
Stefano Sabatini authored
-
Stefano Sabatini authored
According to POSIX, strptime() should consume whitespaces in the date string everytime a whitespace conversion specification is found in the date format specification. Make av_small_strptime() conform with this behavior. In particular, should fix trac ticket #1739.
-
- 05 Sep, 2012 2 commits
-
-
Stefano Sabatini authored
Make internal small_strptime() function public, and use it in place of strptime(). This allows to avoid a dependency on strptime() on systems which do not support it. In particular, fix trac ticket #992.
-
Stefano Sabatini authored
This is consistent with the standard definition of strptime().
-
- 15 Aug, 2012 1 commit
-
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 10 Jul, 2012 1 commit
-
-
Nicolas George authored
Accept 1.1234567 as simply 1.123456 instead of rejecting it. The rounding is towards 0, which is acceptable and much simpler.
-
- 28 Jun, 2012 1 commit
-
-
Paul B Mahol authored
Signed-off-by: Paul B Mahol <onemda@gmail.com>
-
- 20 Jun, 2012 1 commit
-
-
Mans Rullgard authored
Signed-off-by: Mans Rullgard <mans@mansr.com>
-
- 11 Jun, 2012 1 commit
-
-
Stefano Sabatini authored
Make the test independent from the actual error string used to describe a certain error code.
-
- 09 May, 2012 2 commits
-
-
Michael Niedermayer authored
error values can differ between platforms. Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
Michael Niedermayer authored
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 27 Apr, 2012 1 commit
-
-
Nicolas George authored
putenv() seems to be more portable.
-
- 24 Apr, 2012 1 commit
-
-
Reimar Döffinger authored
This should fix the FATE test on ARM (not tested), but it should also detect alpha values like 2^128 reliably as invalid which would be another out-of-range case with implementation-dependant behaviour. Signed-off-by: Reimar Döffinger <Reimar.Doeffinger@gmx.de>
-
- 23 Apr, 2012 3 commits
-
-
Nicolas George authored
-
Nicolas George authored
Until now, av_parse_time() would accept "1:00" as "1" and silently ignore ":00". This patch also includes a few cosmetic changes.
-
Nicolas George authored
-
- 17 Apr, 2012 1 commit
-
-
Nicolas George authored
-
- 28 Mar, 2012 1 commit
-
-
Diego Biurrun authored
Also remove one pointless zero initialization in rangecoder.c.
-
- 06 Feb, 2012 1 commit
-
-
Stefano Sabatini authored
Factorize code and provide ratio parsing consistency.
-
- 16 Nov, 2011 1 commit
-
-
Martin Storsjö authored
This is useful, since the normal timegm function isn't a standard function (requiring _BSD_SOURCE or _SVID_SOURCE on glibc to be visible, and not available on e.g. windows). The widely available function mktime uses the local time zone, which requires ugly workarounds to handle UTC time. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 06 Nov, 2011 1 commit
-
-
Reimar Döffinger authored
All current usages of it are incompatible with localization. For example strcasecmp("i", "I") != 0 is possible, but would break many of the places where it is used. Instead use our own implementations that always treat the data as ASCII. Signed-off-by: Martin Storsjö <martin@martin.st>
-