generic-library/ffmpeg
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

doc/developer: minor typo and consistency fixes

Browse Source 
Signed-off-by: Ganesh Ajjanagadde <gajjanagadde@gmail.com>
This commit is contained in:
Ganesh Ajjanagadde 2015-10-08 09:01:38 -04:00 committed by Stefano Sabatini
parent 8881b035d9
commit 0281ef9075
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/developer.texi
View File

@ -124,10 +124,10 @@ the @samp{inline} keyword;
@samp{//} comments; @samp{//} comments;
@item @item
designated struct initializers (@samp{struct s x = @{ .i = 17 @};}) designated struct initializers (@samp{struct s x = @{ .i = 17 @};});
@item @item
compound literals (@samp{x = (struct s) @{ 17, 23 @};}) compound literals (@samp{x = (struct s) @{ 17, 23 @};}).
@end itemize @end itemize
These features are supported by all compilers we care about, so we will not These features are supported by all compilers we care about, so we will not
@ -156,7 +156,7 @@ GCC statement expressions (@samp{(x = (@{ int y = 4; y; @})}).
All names should be composed with underscores (_), not CamelCase. For example, All names should be composed with underscores (_), not CamelCase. For example,
@samp{avfilter_get_video_buffer} is an acceptable function name and @samp{avfilter_get_video_buffer} is an acceptable function name and
@samp{AVFilterGetVideo} is not. The exception from this are type names, like @samp{AVFilterGetVideo} is not. The exception from this are type names, like
for example structs and enums; they should always be in the CamelCase for example structs and enums; they should always be in CamelCase.
There are the following conventions for naming variables and functions: There are the following conventions for naming variables and functions: