<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>C&#43;&#43;17 on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/c&#43;&#43;17/</link>
    <description>Recent content in C&#43;&#43;17 on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 22 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/c++17/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted C&#43;&#43; Filesystem Libraries: std::filesystem vs ghc::filesystem vs Boost.Filesystem</title>
      <link>https://www.pistack.xyz/posts/2026-06-22-cpp-filesystem-libraries-stdfilesystem-ghcfilesystem-boostfilesystem/</link>
      <pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-22-cpp-filesystem-libraries-stdfilesystem-ghcfilesystem-boostfilesystem/</guid>
      <description>&lt;p&gt;Filesystem operations — traversing directories, checking file permissions, copying and moving files — are fundamental to almost every non-trivial C++ application. Before C++17, developers relied on platform-specific APIs (POSIX &lt;code&gt;dirent.h&lt;/code&gt;, Windows &lt;code&gt;FindFirstFile&lt;/code&gt;) or third-party libraries. The standardization of &lt;code&gt;std::filesystem&lt;/code&gt; in C++17 changed the landscape, but real-world projects still face practical challenges: legacy C++11/14 codebases, incomplete compiler support, and the need for extended functionality beyond the standard.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
