<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Others on Sigasi</title><link>https://www.sigasi.com/tags/others/</link><description>Recent content in Others on Sigasi</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 24 Oct 2011 00:00:00 +0000</lastBuildDate><atom:link href="https://www.sigasi.com/tags/others/index.xml" rel="self" type="application/rss+xml"/><item><title>VHDL case statements can do without the "others"</title><link>https://www.sigasi.com/tech/vhdl-case-statements-can-do-without-others/</link><pubDate>Mon, 24 Oct 2011 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/tech/vhdl-case-statements-can-do-without-others/</guid><description>&lt;p&gt;I was talking to some engineering students the other day, as they were doing a VHDL lab. I noticed a VHDL case statement for state machine with named states (enumerated data type). All states were handled in their VHDL case statement, and still they put an &lt;code&gt;others&lt;/code&gt; section in their code. I had a hard time explaining that this clause was useless. The students mumbled something about their professor eating them alive if they&amp;rsquo;d forget the &lt;code&gt;others&lt;/code&gt; and problems with uninitialized stated and high-impedance state. As you might know, these concepts are related to the &lt;code&gt;std_ulogic&lt;/code&gt; and &lt;code&gt;std_logic&lt;/code&gt; type, but not to enumerated types.&lt;/p&gt;</description></item></channel></rss>