Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: softworkz <ffmpegagent@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Cc: softworkz <softworkz@hotmail.com>
Subject: [FFmpeg-devel] [PATCH] [RFC] global/clang-format: Add .clang-format configuration for consistent formatting
Date: Mon, 21 Apr 2025 23:52:39 +0000
Message-ID: <pull.74.ffstaging.FFmpeg.1745279559776.ffmpegagent@gmail.com> (raw)

From: softworkz <softworkz@hotmail.com>

This is an attempt to create and establish a common definition for
code formatting. Besides .clang-format, there don't seem to be many
good candidates for C when looking for non-proprietary open-source
solutions, so there's wasn't really much choice.

I have tried to configure everything according to the current
guidelines, to which it should come pretty close. There are a few
things for which I couldn't find any FFmpeg rules, or where it wasn't
clear and I made choices that seemed reasonable.

This is in no way intended to prescribe any formatting detail rules,
it's rather meant as an invitation to collaborate on this and ideally
end up with something "official" that allows to check and fix
formatting in CI flows or Patchwork and locally for everybody using
editors with clang-format support or using clang-format from the
command line.

Signed-off-by: softworkz <softworkz@hotmail.com>
---
    [RFC] global/clang-format: Add .clang-format configuration for
    consistent formatting
    
    This is an attempt to create and establish a common definition for code
    formatting. Besides .clang-format, there don't seem to be many good
    candidates for C when looking for non-proprietary open-source solutions,
    so there's wasn't really much choice.
    
    I have tried to configure everything according to the current
    guidelines, to which it should come pretty close. There are a few things
    for which I couldn't find any FFmpeg rules, or where it wasn't clear and
    I made choices that seemed reasonable.
    
    This is in no way intended to prescribe any formatting detail rules,
    it's rather meant as an invitation to collaborate on this and ideally
    end up with something "official" that allows to check and fix formatting
    in CI flows or Patchwork and locally for everybody using editors with
    clang-format support or using clang-format from the command line.
    
    Signed-off-by: softworkz softworkz@hotmail.com

Published-As: https://github.com/ffstaging/FFmpeg/releases/tag/pr-ffstaging-74%2Fsoftworkz%2Fsubmit_clang_format-v1
Fetch-It-Via: git fetch https://github.com/ffstaging/FFmpeg pr-ffstaging-74/softworkz/submit_clang_format-v1
Pull-Request: https://github.com/ffstaging/FFmpeg/pull/74

 .clang-format | 81 +++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 81 insertions(+)
 create mode 100644 .clang-format

diff --git a/.clang-format b/.clang-format
new file mode 100644
index 0000000000..e49e571d48
--- /dev/null
+++ b/.clang-format
@@ -0,0 +1,81 @@
+---
+BasedOnStyle:    GNU
+
+# Alignment & indentation rules
+AlignAfterOpenBracket:               Align
+AlignConsecutiveAssignments:         Consecutive
+AlignConsecutiveDeclarations:        AcrossEmptyLinesAndComments
+AlignArrayOfStructures:              Left
+AlignOperands:                       false
+AlignTrailingComments:               Always
+AlignEscapedNewlines:                LeftWithLastLine
+IndentWidth:                         4
+ContinuationIndentWidth:             4
+UseTab:                              Never
+TabWidth:                            4
+IndentPPDirectives:                  None
+IndentCaseBlocks:                    true
+IndentCaseLabels:                    false
+IndentGotoLabels:                    true
+PointerAlignment:                    Right
+
+AlignConsecutiveShortCaseStatements:
+  Enabled: true
+  AcrossEmptyLines: true
+  AcrossComments: true
+  AlignCaseColons: false
+  
+# Bracing style                      
+BreakBeforeBraces:                   Custom
+BraceWrapping:                       
+  AfterCaseLabel:                    true
+  AfterControlStatement:             Never
+  AfterEnum:                         true
+  AfterFunction:                     true
+  AfterClass:                        false
+  AfterStruct:                       false
+  AfterUnion:                        false
+  AfterExternBlock:                  false
+  BeforeElse:                        false
+  SplitEmptyFunction:                true
+  SplitEmptyRecord:                  true
+BreakAfterReturnType:                None
+
+# Keep lines from becoming too long (adjust to your preference)
+ColumnLimit:                      0
+
+# Misc formatting
+AlwaysBreakAfterReturnType:       None
+BinPackArguments:                 false
+BinPackParameters:                false
+# BinPackLongBracedList:            false
+BreakBeforeTernaryOperators:      true
+InsertNewlineAtEOF:               true
+MaxEmptyLinesToKeep:              2
+AlwaysBreakAfterDefinitionReturnType: None
+
+# Include style
+SortIncludes:                     Never
+IncludeBlocks:                    Preserve
+IncludeCategories:
+  - Regex: '^<.*'
+    Priority: 1
+  - Regex: '^".*'
+    Priority: 2
+  - Regex: '.*'
+    Priority: 3
+
+# Spacing
+SpaceAfterCStyleCast:            false
+SpaceAfterLogicalNot:            false
+SpaceBeforeAssignmentOperators:  true
+SpaceBeforeParens:               ControlStatements
+SpaceBeforeSquareBrackets:       false
+SpaceInEmptyParentheses:         false
+SpacesBeforeTrailingComments:    1
+SpacesInAngles:                  false
+SpacesInConditionalStatement:    false
+SpacesInCStyleCastParentheses:   false
+SpacesInParentheses:             false
+SpacesInSquareBrackets:          false
+...

base-commit: b6c2498a5902766f924cc8728ac65d4fbfd95238
-- 
ffmpeg-codebot
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

             reply	other threads:[~2025-04-21 23:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-21 23:52 softworkz [this message]
2025-04-21 23:56 ` softworkz .

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pull.74.ffstaging.FFmpeg.1745279559776.ffmpegagent@gmail.com \
    --to=ffmpegagent@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=softworkz@hotmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git