<feed xmlns='http://www.w3.org/2005/Atom'>
<title>progmasoft-cpp/Progmasoft_Core_C_Coding_Guidelines/C11, branch main</title>
<subtitle>The C++ style guide of Progmasoft: naming, formatting, language rules, errors, ownership, ABI, testing and tooling.</subtitle>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmasoft-cpp/'/>
<entry>
<title>Give the C sections of the README their own headings</title>
<updated>2026-11-15T14:33:49+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T14:33:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmasoft-cpp/commit/?id=1baf19e8ed000f645028318bec247fb0d5c66936'/>
<id>1baf19e8ed000f645028318bec247fb0d5c66936</id>
<content type='text'>
Codacy's markdownlint found the C section's Contents and The short version
headings repeating those of the C++ section, and a code span that starts
with a space in Comments and documentation.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Codacy's markdownlint found the C section's Contents and The short version
headings repeating those of the C++ section, and a code span that starts
with a space in Comments and documentation.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Write a returned value as 'return (value);'</title>
<updated>2026-11-15T12:47:19+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T12:47:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmasoft-cpp/commit/?id=4decba594424532945a35494f52283515d67b579'/>
<id>4decba594424532945a35494f52283515d67b579</id>
<content type='text'>
clang-format 23 always puts a space after 'return', and no option of the
profile turns it off, so the guidelines take that form: 'return (value);' in
Formatting 2.4, Control flow 5.2, the README and every example. It leaves the
list of what the formatter cannot produce, and clang-format 23.1.5 now
leaves every C block of the chapters unchanged.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
clang-format 23 always puts a space after 'return', and no option of the
profile turns it off, so the guidelines take that form: 'return (value);' in
Formatting 2.4, Control flow 5.2, the README and every example. It leaves the
list of what the formatter cannot produce, and clang-format 23.1.5 now
leaves every C block of the chapters unchanged.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Write Progmasoft Core C Coding Guidelines</title>
<updated>2026-11-15T12:45:44+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T12:45:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmasoft-cpp/commit/?id=fec4661eee5ef6548f9d914a409a496251efcb39'/>
<id>fec4661eee5ef6548f9d914a409a496251efcb39</id>
<content type='text'>
The C11 guidelines take the place of the empty folder, with all eleven
chapters in C11/ since there is one version: principles, formatting with the
.clang-format profile, naming (scope, storage, pointer and direction prefixes,
module prefixes, the meaning of function verbs), files and headers, control
flow, declarations and initializers, preprocessor, memory and ownership, the
C11 language page, comments and Doxygen, and tooling with the .clang-tidy
profile. index.json lists them against the progmasoft-cpp-index schema.

The profile targets clang-format 23. Two settings were added so that it
produces the layout the chapters describe: IncludeIsMainRegex '$^', so a
source file's own header is not moved above the standard ones, and
PenaltyBreakAssignment 100, so a call stays on the line of its '=' and breaks
between its arguments. A list over several lines ends with a comma after its
last item (EnumTrailingComma: Insert for enums): without it clang-format
joins the list or lines it up after the '{'. The forms clang-format 23 cannot
produce are listed in Formatting: 'return(value)', the compound literal
'(Type){ 0 }' and an empty do body.

Every C block of the chapters was checked: clang-format 23.1.5 leaves each
one unchanged except for 'return(value)', and the example module compiles
with clang -std=c11 -pedantic-errors -Wall -Wextra -Werror and passes the
clang-tidy profile.

The C guidelines are a style of their own; a C interface of a C++ library
keeps following the C++ guidelines. README, ADOPTING, LICENSE and the
changelog name them.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The C11 guidelines take the place of the empty folder, with all eleven
chapters in C11/ since there is one version: principles, formatting with the
.clang-format profile, naming (scope, storage, pointer and direction prefixes,
module prefixes, the meaning of function verbs), files and headers, control
flow, declarations and initializers, preprocessor, memory and ownership, the
C11 language page, comments and Doxygen, and tooling with the .clang-tidy
profile. index.json lists them against the progmasoft-cpp-index schema.

The profile targets clang-format 23. Two settings were added so that it
produces the layout the chapters describe: IncludeIsMainRegex '$^', so a
source file's own header is not moved above the standard ones, and
PenaltyBreakAssignment 100, so a call stays on the line of its '=' and breaks
between its arguments. A list over several lines ends with a comma after its
last item (EnumTrailingComma: Insert for enums): without it clang-format
joins the list or lines it up after the '{'. The forms clang-format 23 cannot
produce are listed in Formatting: 'return(value)', the compound literal
'(Type){ 0 }' and an empty do body.

Every C block of the chapters was checked: clang-format 23.1.5 leaves each
one unchanged except for 'return(value)', and the example module compiles
with clang -std=c11 -pedantic-errors -Wall -Wextra -Werror and passes the
clang-tidy profile.

The C guidelines are a style of their own; a C interface of a C++ library
keeps following the C++ guidelines. README, ADOPTING, LICENSE and the
changelog name them.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Add the directories of two more guidelines</title>
<updated>2026-11-13T14:22:50+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-13T14:22:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmasoft-cpp/commit/?id=c9e8341743979c367676b4355c0be1eea8bee211'/>
<id>c9e8341743979c367676b4355c0be1eea8bee211</id>
<content type='text'>
Progmasoft_Core_C_Coding_Guidelines/ with C11/, and
Progmasoft_TalaComponents_Cpp_Coding_Guidelines/ with Cpp17/, kept by
.gitkeep files until their documents are written.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Progmasoft_Core_C_Coding_Guidelines/ with C11/, and
Progmasoft_TalaComponents_Cpp_Coding_Guidelines/ with Cpp17/, kept by
.gitkeep files until their documents are written.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</pre>
</div>
</content>
</entry>
</feed>
