<feed xmlns='http://www.w3.org/2005/Atom'>
<title>progmasoft-cpp, branch docs/core-c-guidelines</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>Merge pull request #4 from Progmasoft/docs/index-schema</title>
<updated>2026-11-15T12:31:25+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-11-15T12:31:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmasoft-cpp/commit/?id=f57d68b8ec3da1f79d7eca6b9eb7679254fcc2f9'/>
<id>f57d68b8ec3da1f79d7eca6b9eb7679254fcc2f9</id>
<content type='text'>
Name the JSON Schema of index.json</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Name the JSON Schema of index.json</pre>
</div>
</content>
</entry>
<entry>
<title>Name the JSON Schema of index.json</title>
<updated>2026-11-15T12:28:42+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T12:28:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmasoft-cpp/commit/?id=ba19afa4f94e8b0ef8a66b4e12fcdd92803ab821'/>
<id>ba19afa4f94e8b0ef8a66b4e12fcdd92803ab821</id>
<content type='text'>
index.json points to https://schemastore.progmasoft.com/json/progmasoft-cpp-index.json
in $schema, so editors check it: the versions with exactly one default, and
every document with its chapter, path and versions. The README and the
changelog link the schema. The file validates against it.

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>
index.json points to https://schemastore.progmasoft.com/json/progmasoft-cpp-index.json
in $schema, so editors check it: the versions with exactly one default, and
every document with its chapter, path and versions. The README and the
changelog link the schema. The file validates against it.

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>Merge pull request #3 from Progmasoft/docs/no-former-language</title>
<updated>2026-11-15T09:15:56+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-11-15T09:15:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmasoft-cpp/commit/?id=ca0f0ffc0dadc7a3fd6476606c99adb2b4c654c6'/>
<id>ca0f0ffc0dadc7a3fd6476606c99adb2b4c654c6</id>
<content type='text'>
Take the examples from Catch3; drop the lowercase-namespace exception</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Take the examples from Catch3; drop the lowercase-namespace exception</pre>
</div>
</content>
</entry>
<entry>
<title>Replace the component guidelines folder with the Chene one</title>
<updated>2026-11-15T09:10:39+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T09:10:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmasoft-cpp/commit/?id=e7138ea61608108795f8a3c6ae8e2180e4bd19bc'/>
<id>e7138ea61608108795f8a3c6ae8e2180e4bd19bc</id>
<content type='text'>
Progmasoft_Chene_Cpp_Coding_Guidelines/ (C++20, not written yet) takes
the place of the C++17 component guidelines folder. The README table and
the changelog say so.

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>
Progmasoft_Chene_Cpp_Coding_Guidelines/ (C++20, not written yet) takes
the place of the C++17 component guidelines folder. The README table and
the changelog say so.

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>Take the examples from Catch3; drop the lowercase-namespace exception</title>
<updated>2026-11-15T09:07:35+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T09:07:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmasoft-cpp/commit/?id=1fce0749209e08033a5e7a35037a9ae00d2c9546'/>
<id>1fce0749209e08033a5e7a35037a9ae00d2c9546</id>
<content type='text'>
Naming 3.4 took its examples and an exception for lowercase intermediate-representation namespaces from a project that is no longer developed. The examples are Catch3's namespaces; the exception is gone, so a project that keeps such a namespace records it as a deviation. ADOPTING.md drops that project's deviation example and its row in the list of projects; the changelog says what changed.

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>
Naming 3.4 took its examples and an exception for lowercase intermediate-representation namespaces from a project that is no longer developed. The examples are Catch3's namespaces; the exception is gone, so a project that keeps such a namespace records it as a deviation. ADOPTING.md drops that project's deviation example and its row in the list of projects; the changelog says what changed.

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>Merge pull request #2 from Progmasoft/docs/guidelines-layout</title>
<updated>2026-11-13T16:19:49+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-11-13T16:19:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmasoft-cpp/commit/?id=84cf683ca325382f4954448ec789db8953636c63'/>
<id>84cf683ca325382f4954448ec789db8953636c63</id>
<content type='text'>
Lay out Progmasoft Core C++ Coding Guidelines as Common, Cpp17 and Cpp20</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Lay out Progmasoft Core C++ Coding Guidelines as Common, Cpp17 and Cpp20</pre>
</div>
</content>
</entry>
<entry>
<title>Use the two names consistently</title>
<updated>2026-11-13T14:38:17+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-13T14:38:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmasoft-cpp/commit/?id=aabd11c1321da173918ad48a2ffb7da5e6d90756'/>
<id>aabd11c1321da173918ad48a2ffb7da5e6d90756</id>
<content type='text'>
Progmasoft C/C++ Styles names the repository, where a text speaks of
all of it: the README introduction, the license texts, CONTRIBUTING and
the changelog. Progmasoft Core C++ Coding Guidelines names its C++
guide, and its own documents call it "the guidelines", in the plural
like its name, instead of "the guide" or "this guide"; the verbs follow.
Dated changelog entries keep their wording. Paragraphs that grew past
120 columns are rewrapped; every link and anchor still resolves.

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 C/C++ Styles names the repository, where a text speaks of
all of it: the README introduction, the license texts, CONTRIBUTING and
the changelog. Progmasoft Core C++ Coding Guidelines names its C++
guide, and its own documents call it "the guidelines", in the plural
like its name, instead of "the guide" or "this guide"; the verbs follow.
Dated changelog entries keep their wording. Paragraphs that grew past
120 columns are rewrapped; every link and anchor still resolves.

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