From 7abd5f3d3f23d8520edb60b6d4d3df9e99fba12b Mon Sep 17 00:00:00 2001 From: simonpj Date: Fri, 25 Oct 2002 15:57:03 +0000 Subject: [PATCH] [project @ 2002-10-25 15:57:03 by simonpj] Reduce exports, and add comments --- ghc/compiler/ghci/Linker.lhs | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/ghc/compiler/ghci/Linker.lhs b/ghc/compiler/ghci/Linker.lhs index 7f34acb..b2e07e3 100644 --- a/ghc/compiler/ghci/Linker.lhs +++ b/ghc/compiler/ghci/Linker.lhs @@ -16,8 +16,9 @@ necessary. {-# OPTIONS -optc-DNON_POSIX_SOURCE #-} module Linker ( HValue, initLinker, showLinkerState, - linkPackages, linkLibraries, findLinkable, - linkModules, unload, extendLinkEnv, linkExpr, + findLinkable, + linkLibraries, linkExpr, + unload, extendLinkEnv, LibrarySpec(..) ) where @@ -630,6 +631,13 @@ linkPackages :: DynFlags -> [PackageName] -> IO () -- (unless of course they are already linked) -- The dependents are linked automatically, and it doesn't matter -- what order you specify the input packages. +-- +-- NOTE: in fact, since each module tracks all the packages it depends on, +-- we don't really need to use the package-config dependencies. +-- However we do need the package-config stuff (to find aux libs etc), +-- and following them lets us load libraries in the right order, which +-- perhaps makes the error message a bit more localised if we get a link +-- failure. So the dependency walking code is still here. linkPackages dflags new_pkgs = do { pls <- readIORef v_PersistentLinkerState -- 1.7.10.4