Commit ee112e9a authored by Mikhail Glushenkov's avatar Mikhail Glushenkov
Browse files

Typos.

Thanks to A. Bram Neijt (see #2045).
parent ecb58796
......@@ -112,8 +112,8 @@ bench args pkg_descr lbi flags = do
ExitFailure _ -> "ERROR")
-- TODO: This is abusing the notion of a 'PathTemplate'. The result
-- isn't neccesarily a path.
-- TODO: This is abusing the notion of a 'PathTemplate'. The result isn't
-- necessarily a path.
benchOption :: PD.PackageDescription
-> LBI.LocalBuildInfo
-> PD.Benchmark
......
......@@ -136,7 +136,7 @@ absolutePackageDBPath (SpecificPackageDB db) =
-- ------------------------------------------------------------
-- | Some compilers support optimising. Some have different levels.
-- For compliers that do not the level is just capped to the level
-- For compilers that do not the level is just capped to the level
-- they do support.
--
data OptimisationLevel = NoOptimisation
......
......@@ -97,12 +97,12 @@ import System.FilePath (splitExtension, dropExtensions, (</>), (<.>),
--
-- The reason for splitting it up this way is that some pre-processors don't
-- simply generate one output .hs file from one input file but have
-- dependencies on other genereated files (notably c2hs, where building one
-- dependencies on other generated files (notably c2hs, where building one
-- .hs file may require reading other .chi files, and then compiling the .hs
-- file may require reading a generated .h file). In these cases the generated
-- files need to embed relative path names to each other (eg the generated .hs
-- file mentions the .h file in the FFI imports). This path must be relative to
-- the base directory where the genereated files are located, it cannot be
-- the base directory where the generated files are located, it cannot be
-- relative to the top level of the build tree because the compilers do not
-- look for .h files relative to there, ie we do not use \"-I .\", instead we
-- use \"-I dist\/build\" (or whatever dist dir has been set by the user)
......
......@@ -295,7 +295,7 @@ configuredPrograms = Map.elems . configuredProgs
--
-- The reason for it not being a failure at this stage is that we don't know up
-- front all the programs we will need, so we try to configure them all.
-- To verify that a program was actually sucessfully configured use
-- To verify that a program was actually successfully configured use
-- 'requireProgram'.
--
configureProgram :: Verbosity
......
......@@ -136,8 +136,8 @@ runTest pkg_descr lbi flags suite = do
pkg_descr lbi n l
}
-- TODO: This is abusing the notion of a 'PathTemplate'. The result
-- isn't neccesarily a path.
-- TODO: This is abusing the notion of a 'PathTemplate'. The result isn't
-- necessarily a path.
testOption :: PD.PackageDescription
-> LBI.LocalBuildInfo
-> PD.TestSuite
......
......@@ -137,8 +137,8 @@ runTest pkg_descr lbi flags suite = do
distPref = fromFlag $ testDistPref flags
verbosity = fromFlag $ testVerbosity flags
-- TODO: This is abusing the notion of a 'PathTemplate'. The result
-- isn't neccesarily a path.
-- TODO: This is abusing the notion of a 'PathTemplate'. The result isn't
-- necessarily a path.
testOption :: PD.PackageDescription
-> LBI.LocalBuildInfo
-> PD.TestSuite
......
......@@ -1018,7 +1018,7 @@ withFileContents name action =
-- | Writes a file atomically.
--
-- The file is either written sucessfully or an IO exception is raised and
-- The file is either written successfully or an IO exception is raised and
-- the original file is left unchanged.
--
-- On windows it is not possible to delete a file that is open by a process.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment