<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cmdliner on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/cmdliner/</link>
    <description>Recent content in Cmdliner on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 15 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/cmdliner/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OCaml CLI Parsing in 2026: Cmdliner vs Core.Command vs Arg — Which One Survives a Real Tool?</title>
      <link>https://www.pistack.xyz/posts/2026-11-15-ocaml-cli-frameworks-cmdliner-arg-core-command/</link>
      <pubDate>Sun, 15 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-15-ocaml-cli-frameworks-cmdliner-arg-core-command/</guid>
      <description>&lt;p&gt;Every OCaml tool starts the same way: a quick &lt;code&gt;Arg.parse&lt;/code&gt; that takes twenty lines and works fine. Eighteen months later that tool has subcommands, environment-variable fallbacks, a &lt;code&gt;--json&lt;/code&gt; output mode, and a &lt;code&gt;--help&lt;/code&gt; page nobody has read since the first commit. The argument parser you picked on day one is now the reason your users cannot discover a flag that has existed for a year.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
