<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>File Structure on Sigasi</title><link>https://www.sigasi.com/tags/file-structure/</link><description>Recent content in File Structure on Sigasi</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 28 Sep 2009 00:00:00 +0000</lastBuildDate><atom:link href="https://www.sigasi.com/tags/file-structure/index.xml" rel="self" type="application/rss+xml"/><item><title>How to organize source code? Learn from Java.</title><link>https://www.sigasi.com/legacy/tech/how-organize-source-code-learn-java/</link><pubDate>Mon, 28 Sep 2009 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/legacy/tech/how-organize-source-code-learn-java/</guid><description>&lt;p&gt;Since most HDLs do not force you to use a specific directory structure in your projects, each organization is left with the burden to &lt;a
 style="white-space: nowrap;"
 href="https://www.sigasi.com/legacy/tech/how-do-you-organize-source-code-your-hardware-project/"
 
 &gt;devise its own conventions&lt;/a&gt;. This post describes directory and file naming conventions, learned from the &lt;a
 style="white-space: nowrap;"
 href="https://www.oracle.com/java/technologies/"
 
 target="_blank"
 
 &gt;Java&amp;nbsp;&lt;span uk-icon="icon: sign-out; ratio: 0.7"&gt;&lt;/span&gt;&lt;/a&gt; programming language.&lt;/p&gt;</description></item><item><title>How do you organize the source code of your hardware project?</title><link>https://www.sigasi.com/legacy/tech/how-do-you-organize-source-code-your-hardware-project/</link><pubDate>Fri, 25 Sep 2009 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/legacy/tech/how-do-you-organize-source-code-your-hardware-project/</guid><description>&lt;p&gt;Some computer languages force a certain directory structure upon its users. While this may seem like a restriction of your freedom, in fact well-chosen directory conventions give you the liberty to concentrate on more important matters. Regrettably, languages like C and VHDL leave their users with total freedom to make bad choices about their file structures. Since you don&amp;rsquo;t get rules enforced by the language, you are faced with the choice between either total chaos or composing your own guidelines for filenames and directory structures. If you choose the latter, some lessons are to be learned from other computer languages&amp;rsquo; conventions, as well as from publicly available VHDL sources.&lt;/p&gt;</description></item></channel></rss>