After considering the different options (specially Yhc.Core) I decided
to go for Embedded Compiling [1] + Observable Sharing[2] to translate
from ForSyDe[3] to VHDL[4] instead of making a whole Haskell-Compiler
backend.
Creating a backend would fit a more ambitious goal: translating any
haskell source file to VHDL, and of course would be more difficult to
approach.
The drawback of the Embedded Compiler approach is that ForSyDe will
need to be adapted. But instead the translation would be quite easy to
make and what is more important, a lot more maintainable due to being
independent of external tools and embedded in the library itself.
Thanks a lot for your suggestions. Specially to Neil who is
fortunately always open to help.
References
[1] http://haskell.org/haskellwiki/Research_papers/Domain_specific_languages
[2] http://www.cs.chalmers.se/~koen/pubs/entry-asian99-lava.html
[3] http://www.imit.kth.se/info/FOFU/ForSyDe/
[4] http://en.wikipedia.org/wiki/VHDL
On 11/12/06, Alfonso Acosta <alfonso.acosta at gmail.com> wrote:
> > For .hi files just compile it with Yhc and take a look at the .hi file
> > it creates, they are plain text. If they are top level functions
> > (which they certainly are, I guess) this should be all you need.
> > Another approach is to get the type information out of Hugs with the
> > :t command line prod. I've done this before in another project.
>> Sorry for the delay answering. I didn't (and still won't) have access
> to the Internet for a few days but Ill try it and tell you if it
> worked once I'm back to normality.
>> Thanks,
>> Alfonso Acosta
>