long long is already being used in quite a few places in FFmpeg. There is no reason to list it as something to avoid. Or put in other words, it is definitely out of place in the surrounding context.
Signed-off-by: Ganesh Ajjanagadde <gajjanaga...@gmail.com> --- doc/developer.texi | 3 --- 1 file changed, 3 deletions(-) diff --git a/doc/developer.texi b/doc/developer.texi index 455b120..afc707a 100644 --- a/doc/developer.texi +++ b/doc/developer.texi @@ -146,9 +146,6 @@ additional C99 features or GCC extensions. Especially watch out for: mixing statements and declarations; @item -@samp{long long} (use @samp{int64_t} instead); - -@item @samp{__attribute__} not protected by @samp{#ifdef __GNUC__} or similar; @item -- 2.6.2 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel