here are some of the things that might need or want to be done,
extending from my task of making GHC code more portable (which
thankfully other people are helping with too, e.g. by cleaning up warnings!)
- not just ghc/compiler Haskell code; at least the makefile system needs
not to use specific ghc flags when not using ghc as compiler
- alex/happy
- implement LANGUAGE, PatternGuards in Jhc
- hopefully perhaps the nonportable/base GHC.* modules can be split off
into another package somehow, but this is probably someone else's territory
- look into nhc or yhc
- make sure Cabal can handle it
- reduce #ifdef platforms in GHC code... I should think that GHC could
be able to be, at least, compiled as a cross-compiler. Compiling to
some unregisterised .hc that could be compiled and linked with other .c
on any platform would be nice -- is it at all possible? -- though it
would possibly impact performance by making some things non-constant.
- minimum hoped-for goal: make bootstrapping on new platforms be able to
be easier, less ad-hoc (either unregisterised or you have to write an
NCG, I suppose, but anyway.)
Do you think it's plausible to apply for this as haskell.org Summer of
Code project (I'm a U.S. college student now, which explains why I've
been too busy to work on GHC stuff, and in the fall) ; I don't know much
about the process, and of course there's lots of competition, but, any
advice?
-Isaac
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
