this not been done before?}. Using a functional language for describing hardware
is not a new idea at all. In fact, there has been research into functional
hardware description even before the conventional hardware description
- languages were created. Examples of these are µFP \cite[sheeran83] and
+ languages were created. Examples of these are µFP \cite[sheeran83]\ and
Ruby \cite[jones90]. Functional languages were not nearly as advanced
as they are now, and functional hardware description never really got
off.
Recently, there have been some renewed efforts, especially using the
- Haskell functional language. Examples are Lava \cite[claessen00] (an
- \small{EDSL}) and ForSyde \cite[sander04] (an \small{EDSL} using
- Template Haskell). \cite[baaij09] has a more complete overview of the
+ Haskell functional language. Examples are Lava \cite[claessen00]\ (an
+ \small{EDSL}) and ForSyde \cite[sander04]\ (an \small{EDSL} using
+ Template Haskell). \cite[baaij09]\ has a more complete overview of the
current field.
We will now have a look at the existing hardware description languages,
embedded functional hardware description languages (in particular
those using Haskell) are limited. Below a number of downsides are
sketched of the recent attempts using the Haskell language.
- \cite[baaij09] has a more complete overview of these and other
+ \cite[baaij09]\ has a more complete overview of these and other
languages.
This list uses Lava and ForSyDe as examples, but tries to generalize