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
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 d
Hi
That implies I need a way to infere or directly obtain the types of
the functions used in the core representation. That as you said, can
probably be done by means of the .hi files or the typerep extension
you mentioned. I'll try to have a look at both options. Any good
documentation pointers?
On 11/6/06, Neil Mitchell <[EMAIL PROTECTED]> wrote:
Can you explain more about the "declare the interface" remark? I
suspect this can be acheived with Yhc using the signatures from the
.hi files, or embeding the information with our "typerep" Haskell
extension.
I think you're correctly suspect
Hi
I haven't yet planned how to achieve the translation but VHDL, unlike
Haskell, doesn't have type inference mechanisms. That means I need to
declare the interface of whatever I will translate each Yhc.Core
function to (i.e. VHDL Entities, Architectures, Functions ... )
Can you explain more a
| In order to get part of the work for free I decided to design the
| translator as a compiler backend. The best option so far seems to be
| Yhc's Core API (http://haskell.org/haskellwiki/Yhc/API/Core ), which
| unfortunately lacks type information.
|
| I discarded GHC due to the current "bit-rott
On 11/6/06, Neil Mitchell <[EMAIL PROTECTED]> wrote:
Can you mention what you need type information for? If it is to detect
higher order functions (as you have mentioned in IRC conversations
with me) then in about a week I am going to announce a Yhc.Core first
order transformation, which will rem
Hi
In order to get part of the work for free I decided to design the
translator as a compiler backend. The best option so far seems to be
Yhc's Core API (http://haskell.org/haskellwiki/Yhc/API/Core ), which
unfortunately lacks type information.
Can you mention what you need type information fo
Hi all,
As I wrote in the previous HLADPSA announcement, during the following
moths I'm going to write a translator from Haskell to VHDL in order to
accomplish my masters thesis goal.
The main requirement is managing to translate from a ForSyDe
(http://www.imit.kth.se/info/FOFU/ForSyDe/ ) specif