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
0281ef90
Commit
0281ef90
authored
Oct 08, 2015
by
Ganesh Ajjanagadde
Committed by
Stefano Sabatini
Oct 10, 2015
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc/developer: minor typo and consistency fixes
Signed-off-by:
Ganesh Ajjanagadde
<
gajjanagadde@gmail.com
>
parent
8881b035
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
developer.texi
doc/developer.texi
+3
-3
No files found.
doc/developer.texi
View file @
0281ef90
...
@@ -124,10 +124,10 @@ the @samp{inline} keyword;
...
@@ -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; @})}).
...
@@ -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:
...
...
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