On 3/17/08, John Meacham
Well, it depends. Ideally what I want is for the 'jhc' distribution to contain just the haskell' libraries (once they are finalized) which will likely be much smaller than the current extended 'base' that ghc uses, so I don't want to get in the habit of importing code from the ghc repo in large quantities.
that said, for practical reasons, and since a lot of the stuff in ghc base isn't separately packaged, I do need some way to make it available. I think what would be best is to have the current 'base' library just contain a fairly minimal base, what we expect to be in haskell' or what is jhc specific enough to be interesting.as well as what is enough to build 'haskell98'. then create another 'base-extras' library which will contain mostly unchanged code from the ghc repo that is in ghc's base. like System.Console.GetOpts can probably go there.
Wouldn't it be more sensible to put the JHC-specific code in a library called jhcbase, like hugs does (only of course theirs is called hugsbase or something), and just use the "base" repository that everyone else uses for the not-really-jhc-specific bits?