#3559: split ghci modules off into their own package
---------------------------------+------------------------------------------
Reporter: igloo | Owner:
Type: task | Status: new
Priority: normal | Milestone: 6.14.1
Component: GHCi | Version: 6.10.4
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Testcase: | Os: Unknown/Multiple
Architecture: Unknown/Multiple |
---------------------------------+------------------------------------------
Comment (by simonmar):
I don't think we can split off a separate ghci package, because it would
be mutually recursive with the ghc package. The main reason for the GHCI
`#ifdef` is that we can only use GHCi in stage 2 when the libraries we
dynamically load are the same as the ones that GHC itself is linked with,
so that data representations etc. are compatible. We never ship a `ghc`
package without GHCi support, so clients don't need to worry about this.
Now, it's possible we could pull enough code out from inside GHCI to fix
the Haddock issue described above, and that's not a bad thing. But I
don't think this is an issue that affects any other clients.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3559#comment:1>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
