<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Legacy-Systems on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/legacy-systems/</link>
    <description>Recent content in Legacy-Systems on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 16 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/legacy-systems/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tcl Testing in 2026: tcltest vs Expect vs DejaGnu — Which Harness Fits Your Legacy Stack?</title>
      <link>https://www.pistack.xyz/posts/2026-11-16-tcl-testing-tcltest-expect-dejagnu-comparison/</link>
      <pubDate>Mon, 16 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-16-tcl-testing-tcltest-expect-dejagnu-comparison/</guid>
      <description>&lt;p&gt;Tcl is not a hobby language. It is embedded in EDA toolchains, network device automation, storage arrays, and the test suites of projects as widely deployed as SQLite. That means a very specific career moment keeps repeating: you inherit 40,000 lines of Tcl, nobody remembers how the test suite is supposed to run, and &lt;code&gt;make test&lt;/code&gt; prints either nothing or a wall of failures with no summary.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
