Hi Ulrich,
Unfortunately I no longer have any time to work on Yhc, and don't have
any easy answers to your problems. Someone at the yhc@ mailing list
may have the answers, but the number of Yhc developers is pretty small
(possibly 0), so you may not have much success.
Thanks
Neil
On Sat, Jan 10, 2009 at 12:43 PM, Ulrich Vollert <ulrich(a)vollert.net> wrote:
> Hi Neil,
>
> I tried to build Yhc on my Sharp Zaurus C-3200
> (http://www.pulster.de/engl/sharp_zaurus_c-1000_3200.htm)
>
> The Zaurus is run by Debian Linux 2.6.24 and there are all the tools needed
> for Yhc: gcc 4.3.2, scons (v1.0.0.r3266), Python 2.5.2, darcs 2.1.0 and
> (even !) ghc 6.8.2.
>
> Okay, ghc is a bit heavy for this small machine but it works ;-)
>
> Unfortunately I cant build Yhc. After "scons configure" I get:
>
> <<Unknow armv5tel - Your architectecture is unsupported.>>
>
> Any chance to build Yhc?
>
> Regards,
> Ulrich
>
>
>
>
>
I'm trying to map lambda names in Yhc Core code back to the containing
functions, but there doesn't seem to be any obvious way of doing this.
I was wondering if anyone had any ideas.
I've spotted a previous mailing list post
(http://www.haskell.org/pipermail/yhc/2007-June/000957.html) and a
google code bug (http://code.google.com/p/yhc/issues/detail?id=141) but
no evidence of anything having been done.
Does anyone have any ideas what naming would be nice? Given:
module Test where
main = (\a -> a) 42
presumably we want something like Test;main!LAMBDAxxx - with whatever
seperator seems nice. Using a different symbol has the same
reasoning as using the ";" - to make it easy for Yhc Core based tools,
see (http://www.haskell.org/pipermail/yhc/2007-August/001044.html)
As far as implementing this goes, it seems that liftLambda in Lift.hs
is naming the function, but I can't work out where the code it is
lifting came from. Any pointers on that would be appreciated.
Thanks
