Refactoring, tidyup and improve layering
authorSimon Marlow <simonmar@microsoft.com>
Wed, 2 May 2007 13:54:34 +0000 (13:54 +0000)
committerSimon Marlow <simonmar@microsoft.com>
Wed, 2 May 2007 13:54:34 +0000 (13:54 +0000)
commit86bec4298d582ef1d8f0a201d6a81145e1be9498
treeee095c23e7539ff9853214c44cb099572e21008e
parent065ce67b1b6ba6b8f3646b73c7cadd50a001a9af
Refactoring, tidyup and improve layering

The stack of breakpoint resume contexts is now part of the
InteractiveContext and managed by the GHC API.  This prevents misuse
of the resume context by the client (e.g. resuming a breakpoint that
isn't the topmost, which would lead to a confused IC at the least).

I changed the TypeEnv in the IC to a [Id].  It only contained Ids
anyway, and this allows us to have shadowing, which removes an ugly
and annoying restriction.

The parts of the GHC API which deal with interactive evaluation are
now in a module of their own, InteractiveEval.
compiler/ghci/ByteCodeInstr.lhs
compiler/ghci/Debugger.hs
compiler/ghci/GhciMonad.hs
compiler/ghci/InteractiveUI.hs
compiler/main/GHC.hs
compiler/main/HscMain.lhs
compiler/main/HscTypes.lhs
compiler/main/InteractiveEval.hs [new file with mode: 0644]
compiler/main/InteractiveEval.hs-boot [new file with mode: 0644]
compiler/typecheck/TcRnDriver.lhs