RepoMirrors
/
ffmpeg
mirror of https://git.ffmpeg.org/ffmpeg.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

all non trivial functions, structurs and their member variables should be documented 

Originally committed as revision 3313 to svn://svn.ffmpeg.org/ffmpeg/trunk
This commit is contained in:
Michael Niedermayer 2004-07-14 13:07:23 +00:00
parent bb0b93ba81
commit 80d1c272be
1 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/ffmpeg-doc.texi
View File

@ -944,6 +944,7 @@ You can use libavcodec or libavformat in your commercial program, but
@emph{any patch you make must be published}. The best way to proceed is
to send your patches to the ffmpeg mailing list.
@node Coding Rules
@section Coding Rules
ffmpeg is programmed in the ISO C90 language with a few additional
@ -985,15 +986,20 @@ The presentation is the one specified by 'indent -i4 -kr'.
Main priority in ffmpeg is simplicity and small code size (=less
bugs).
Comments: for functions visible from other modules, use the JavaDoc
format (see examples in @file{libav/utils.c}) so that a documentation
can be generated automatically.
Comments: use the JavaDoc/Doxygen
format (see examples in @file{libavformat/utils.c}) so that a documentation
can be generated automatically. All non trivial functions should have a comment
above it explaining what the function does, even if its just one sentance.
All Structures and their member variables should be documented too.
fprintf and printf are forbidden in libavformat and libavcodec,
please use av_log() instead.
@section Submitting patches
First, (@pxref{Coding Rules}) above if you didn't yet.
When you submit your patch, try to send a unified diff (diff '-up'
option). I cannot read other diffs :-)