Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in / Register
Toggle navigation
F
ffmpeg.wasm-core
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Linshizhi
ffmpeg.wasm-core
Commits
acf22ec6
Commit
acf22ec6
authored
Dec 03, 2011
by
Michael Niedermayer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
developer.texi: Fix naming convention
Signed-off-by:
Michael Niedermayer
<
michaelni@gmx.at
>
parent
52b7ed4f
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
developer.texi
doc/developer.texi
+2
-2
No files found.
doc/developer.texi
View file @
acf22ec6
...
...
@@ -141,8 +141,8 @@ GCC statement expressions (@samp{(x = (@{ int y = 4; y; @})}).
@subsection Naming conventions
All names are using underscores (
_
), not CamelCase. For example, @samp
{
avfilter
_
get
_
video
_
buffer
}
is
a valid function name and @samp
{
AVFilterGetVideo
}
is not. The
only exception from this are structure names;
they should always be in the CamelCase
a valid function name and @samp
{
AVFilterGetVideo
}
is not. The
exception from this are type names, like
for example structs and enums;
they should always be in the CamelCase
There are following conventions for naming variables and functions:
@itemize @bullet
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment