[FFmpeg-cvslog] r25385 - trunk/libavformat/mpegenc.c

[Diego Biurrun]

Sorry, fingers slipped ('y' instead of 'q y' in mutt) and this draft
message was sent off unfinished, when I was just thinking I should
probably not send it and think it through better...

On Fri, Oct 08, 2010 at 11:35:57AM +0200, Diego Biurrun wrote:
> On Thu, Oct 07, 2010 at 09:40:39PM +0200, Michael Niedermayer wrote:
> > 
> > Anyway i will try to add some whitespace to be closer to indent -kr
> 
> How about these simple to follow rules (excerpted from a guide I was
> asked to write @work):
> 
> - spacing:
>   In general use spaces generously, i.e. place a space
> 
>     * between keywords and '(' (except for sizeof),
>     * between ')' and '{',
>     * around assignment and logical operators (=, +=, |=, &, &&, ||,..),
>     * after ',' - for example in function arguments.
> 
>   but avoid spaces
> 
>     * between function names and '(',
>     * inside '()'.
> 
> - brace placement:
>   Opening braces should be kept on the same line as the corresponding
>   statement, except for functions where the opening brace is placed
>   on the next line.
> 
> - case statements are not indented separately, they remain at the
>   same level as the corresponding switch statement.
> 
> - The function type should be kept on the same line as the function
>   name.
> 
> - pointer stars go with the variable name,
>   i.e. 'char *str' vs. 'char* str'
> 
> int foo(int arg, void *parm)
> {
>     char *var1;
> 
>     if (arg == 23)
>         var1 = "success!\n";
> }
> 
> Diego
> _______________________________________________
> ffmpeg-cvslog mailing list
> ffmpeg-cvslog at mplayerhq.hu
> https://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-cvslog