[vlc-devel] commit: vlc: Code conventions. (Pierre d'Herbemont )
Rémi Denis-Courmont
rdenis at simphalempin.com
Thu May 15 22:42:23 CEST 2008
Le Thursday 15 May 2008 23:30:52 Rafaël Carré, vous avez écrit :
> Le Thu, 15 May 2008 22:19:14 +0200 (CEST),
>
> git at videolan.org (git version control) a écrit :
> > vlc | branch: master | Pierre d'Herbemont <pdherbemont at videolan.org>
> >
> > | Thu May 15 22:19:43 2008 +0200|
> >
> > [42255fd0692bc9d4b4155728c1f390301a9f19e6]
> >
> > vlc: Code conventions.
> >
> > > http://git.videolan.org/gitweb.cgi/vlc.git/?a=commit;h=42255fd0692bc9d4
> > >b4155728c1f390301a9f19e6
> >
> > ---
> >
> > - if (vlc) libvlc_release( vlc );
> > + if (vlc) libvlc_release (vlc);
>
> I don't remember seeing this convention.
Neither do I.
But VLC disagrees with the world few undisputed coding styles. You know people
disagree an spaces vs tabs and the size of tasbs, on the width of a line, on
how to wrap overly long lines, on whether statement block braces deserve an
empty line of their own, on whether single statement blocks should have
braces or not, on whether there is a space between a function name and the
opening parenthesis, on whether to use_underscore_function_names or
CapitalLettersFunctionNames. Also few other people still believe in the
hungarian notation (at least Win32, but that's not a reference).
BUT - everybody agrees that there is no space between the opening parenthesis
and the first parameter, nor between the last parameter and the closing
parenthesis.
--
Rémi Denis-Courmont
http://www.remlab.net/
More information about the vlc-devel
mailing list