|
|
|
|
Synopsis |
|
|
|
Documentation |
|
env |
|
withModEnv :: Env -> (ModEnv -> IO a) -> IO a | Source |
|
apply f to the loaded objects Env, apply f to the package.conf
FM locks up the MVar so you can't recursively call a function
inside a with any -Env function. Nice and threadsafe
|
|
withDepEnv :: Env -> (DepEnv -> IO a) -> IO a | Source |
|
|
withPkgEnvs :: Env -> (PkgEnvs -> IO a) -> IO a | Source |
|
|
withMerged :: Env -> (MergeEnv -> IO a) -> IO a | Source |
|
|
|
|
|
|
modifyPkgEnv :: Env -> (PkgEnvs -> IO PkgEnvs) -> IO () | Source |
|
|
modifyMerged :: Env -> (MergeEnv -> IO MergeEnv) -> IO () | Source |
|
|
|
insert a loaded module name into the environment
|
|
|
remove a module name from the environment. Returns True if the
module was actually removed.
|
|
|
insert a list of module names all in one go
|
|
|
is a module/package already loaded?
|
|
|
|
|
Set the dependencies of a Module.
|
|
|
Get module dependencies. Nothing if none have been recored.
|
|
|
Unrecord a module from the environment.
|
|
|
|
|
|
|
|
|
Insert a single package.conf (containing multiple configs) means:
create a new FM. insert packages into FM. add FM to end of list of FM
stored in the environment.
|
|
|
add a new FM for the package.conf to the list of existing ones
|
|
|
|
|
|
|
generate a PkgEnv from the system package.conf
The path to the default package.conf was determined by configure
This imposes a constraint that you must build your plugins with the
same ghc you use to build hs-plugins. This is reasonable, we feel.
|
|
|
|
|
|
Produced by Haddock version 2.4.2 |