Yhc/TMR: Difference between revisions
NeilMitchell (talk | contribs) |
NeilMitchell (talk | contribs) No edit summary |
||
| Line 3: | Line 3: | ||
This is a draft of the Yhc TMR article, deadline April 13th. It isn't intended as a wiki article beyond the listed authors (although if you want to fix some spelling, we don't mind!). If you are interested in helping email the Yhc list. | This is a draft of the Yhc TMR article, deadline April 13th. It isn't intended as a wiki article beyond the listed authors (although if you want to fix some spelling, we don't mind!). If you are interested in helping email the Yhc list. | ||
= | = The Beginning = | ||
In the beginning there was the nhc compiler, which had a number of issues. We fixed some of them. | |||
Author: Tom/Neil/Andrew | Author: Tom/Neil/Andrew | ||
| Line 12: | Line 14: | ||
= Portability Concerns = | = Portability Concerns = | ||
From the beginning portability was a prime concern, while the original nhc was only running on Linux v old.old, and never Windows, Yhc was fully portable by design. | |||
Author: Tom, Andrew | Author: Tom, Andrew | ||
| Line 17: | Line 21: | ||
Why portability is such a concern, details of our ports system. Include our scons architecture, buildbot system etc. Mention that Yhc runs under Hugs, and indeed some of the developers use Hugs. | Why portability is such a concern, details of our ports system. Include our scons architecture, buildbot system etc. Mention that Yhc runs under Hugs, and indeed some of the developers use Hugs. | ||
= | = Why the front end must die, Libraries for All = | ||
Lots of the nhc features are pure evil. We should rewrite them to move forward, making the compiler more compliant and more friendly for all. Libraries would be a good strategy. | |||
Author: Neil/Tom | Author: Neil/Tom | ||
| Line 30: | Line 30: | ||
= Yhc.Core = | = Yhc.Core = | ||
Yhc.Core is one area we have already moved into the library field, and its getting used quite a lot. | |||
Author: Neil (with bits from Matt, Dimitry) | Author: Neil (with bits from Matt, Dimitry) | ||
| Line 36: | Line 38: | ||
= Javascript Backend = | = Javascript Backend = | ||
The Javascript backend is a unique feature of Yhc, something which our light weight approach makes easier. | |||
Author: Dimitry | Author: Dimitry | ||
the ideas behind it, the Javascript FFI, browser compatability, the approach | the ideas behind it, the Javascript FFI, browser compatability, the approach | ||
= Wacky Features = | |||
Yhc is going in many interesting directions. Some of these directions are likely to become very important in the future, some are likely to fade away. Yhc is a genuine research bed for brand new ideas. | |||
Author: All | |||
When you don't spend all the time on wacky type systems, you get a lot more time left to work on Wacky other stuff. Include Java interpetter, .NET back end, Javascript back end, Python interpretter, Hat debugging, yhi-stack, whole program optimisation. Lots of these things are breeding grounds for various useful technologies, and most are marching towards genuine usefulness. | |||
Revision as of 15:47, 20 February 2007
Authors: Neil Mitchell, Tom Shackell, Matt Naylor, Dimitry Golubovsky, Andrew Wilkinson
This is a draft of the Yhc TMR article, deadline April 13th. It isn't intended as a wiki article beyond the listed authors (although if you want to fix some spelling, we don't mind!). If you are interested in helping email the Yhc list.
The Beginning
In the beginning there was the nhc compiler, which had a number of issues. We fixed some of them.
Author: Tom/Neil/Andrew
How we started up Yhc, this is the section that would have been in the History of Haskell paper if they had done a Yhc section :)
Include the transition from CVS -> york Darcs -> haskell.org Darcs
Portability Concerns
From the beginning portability was a prime concern, while the original nhc was only running on Linux v old.old, and never Windows, Yhc was fully portable by design.
Author: Tom, Andrew
Why portability is such a concern, details of our ports system. Include our scons architecture, buildbot system etc. Mention that Yhc runs under Hugs, and indeed some of the developers use Hugs.
Why the front end must die, Libraries for All
Lots of the nhc features are pure evil. We should rewrite them to move forward, making the compiler more compliant and more friendly for all. Libraries would be a good strategy.
Author: Neil/Tom
Our thoughts on the future, kill the front end and turn everything into a library. Keep the compiler light weight,
Yhc.Core
Yhc.Core is one area we have already moved into the library field, and its getting used quite a lot.
Author: Neil (with bits from Matt, Dimitry)
Why Yhc.Core is so very important, a list of the projects that use it. Why Yhc Core is better than GHC Core - i.e. the only option left around.
Javascript Backend
The Javascript backend is a unique feature of Yhc, something which our light weight approach makes easier.
Author: Dimitry
the ideas behind it, the Javascript FFI, browser compatability, the approach
Wacky Features
Yhc is going in many interesting directions. Some of these directions are likely to become very important in the future, some are likely to fade away. Yhc is a genuine research bed for brand new ideas.
Author: All
When you don't spend all the time on wacky type systems, you get a lot more time left to work on Wacky other stuff. Include Java interpetter, .NET back end, Javascript back end, Python interpretter, Hat debugging, yhi-stack, whole program optimisation. Lots of these things are breeding grounds for various useful technologies, and most are marching towards genuine usefulness.