<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Uncrustify on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/uncrustify/</link>
    <description>Recent content in Uncrustify on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 27 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/uncrustify/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>C&#43;&#43; Code Formatting Tools: clang-format vs Uncrustify vs Astyle</title>
      <link>https://www.pistack.xyz/posts/2026-06-27-cpp-code-formatting-tools-clang-format-uncrustify-astyle/</link>
      <pubDate>Sat, 27 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-27-cpp-code-formatting-tools-clang-format-uncrustify-astyle/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Consistent code formatting is one of the highest-leverage investments a development team can make — it eliminates bikeshedding over brace placement, reduces cognitive load during code review, and ensures every contributor produces code that looks like it belongs. For self-hosted C++ projects, automated formatting tools running in CI/CD pipelines enforce style rules mechanically, freeing developers to focus on logic rather than layout.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
