<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Posts on System Verilog Case Statement</title>
    <link>https://system-verilog-case-statement.pages.dev/posts/</link>
    <description>Recent content in Posts on System Verilog Case Statement</description>
    <image>
      <title>System Verilog Case Statement</title>
      <url>https://tse1.mm.bing.net/th?q=system%20verilog%20case%20statement</url>
      <link>https://tse1.mm.bing.net/th?q=system%20verilog%20case%20statement</link>
    </image>
    <generator>Hugo -- 0.151.1</generator>
    <language>en</language>
    <lastBuildDate>Sun, 03 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://system-verilog-case-statement.pages.dev/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Getting the System Verilog Case Statement Right</title>
      <link>https://system-verilog-case-statement.pages.dev/posts/system-verilog-case-statement/</link>
      <pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate>
      <guid>https://system-verilog-case-statement.pages.dev/posts/system-verilog-case-statement/</guid>
      <description>Writing clean code often starts with how you handle the system verilog case statement in your design. If you&amp;#39;ve spent any time debugging RTL, you know that logic branching is where most of the &amp;#39;weird&amp;#39; bugs hide. You think you&amp;#39;ve covered every</description>
    </item>
  </channel>
</rss>
