filepath 1.4.1.1 → 1.4.1.2

raw patch · 4 files changed

+11/−7 lines, 4 filesdep ~basePVP ok

version bump matches the API change (PVP)

Dependency ranges changed: base

API changes (from Hackage documentation)

Files

• LICENSE +1/−1
• README.md +1/−1
• changelog.md +4/−0
• filepath.cabal +5/−5

@@ -1,4 +1,4 @@-Copyright Neil Mitchell 2005-2016.+Copyright Neil Mitchell 2005-2017. All rights reserved.  Redistribution and use in source and binary forms, with or without

@@ -12,7 +12,7 @@  The answer for this library is "no". While an abstract `FilePath` has some advantages (mostly type safety), it also has some disadvantages: -* In Haskell the definition is `type FilePath = String`, and all file-orientated functions operate on this type alias, e.g. `readFile`/`writeFile`. Any abstract type would require wrappers for these functions or lots of casts between `String` and the abstraction.+* In Haskell the definition is `type FilePath = String`, and all file-oriented functions operate on this type alias, e.g. `readFile`/`writeFile`. Any abstract type would require wrappers for these functions or lots of casts between `String` and the abstraction. * It is not immediately obvious what a `FilePath` is, and what is just a pure `String`. For example, `/path/file.ext` is a `FilePath`. Is `/`? `/path`? `path`? `file.ext`? `.ext`? `file`? * Often it is useful to represent invalid files, e.g. `/foo/*.txt` probably isn't an actual file, but a glob pattern. Other programs use `foo//bar` for globs, which is definitely not a file, but might want to be stored as a `FilePath`. * Some programs use syntactic non-semantic details of the `FilePath` to change their behaviour. For example, `foo`, `foo/` and `foo/.` are all similar, and refer to the same location on disk, but may behave differently when passed to command-line tools.

@@ -2,6 +2,10 @@  _Note: below all `FilePath` values are unquoted, so `\\` really means two backslashes._ +## 1.4.1.2  *Feb 2017*++ * Bundled with GHC 8.2.1+ ## 1.4.1.1  *Nov 2016*   * Bundled with GHC 8.0.2

@@ -1,18 +1,18 @@-cabal-version:  >= 1.10+cabal-version:  >= 1.18 name:           filepath-version:        1.4.1.1+version:        1.4.1.2 -- NOTE: Don't forget to update ./changelog.md license:        BSD3 license-file:   LICENSE author:         Neil Mitchell <ndmitchell@gmail.com> maintainer:     Neil Mitchell <ndmitchell@gmail.com>-copyright:      Neil Mitchell 2005-2016+copyright:      Neil Mitchell 2005-2017 bug-reports:    https://github.com/haskell/filepath/issues homepage:       https://github.com/haskell/filepath#readme category:       System build-type:     Simple synopsis:       Library for manipulating FilePaths in a cross platform way.-tested-with:    GHC==8.0.1, GHC==7.10.3, GHC==7.8.4, GHC==7.6.3, GHC==7.4.2+tested-with:    GHC==8.0.2, GHC==7.10.3, GHC==7.8.4, GHC==7.6.3, GHC==7.4.2 description:     This package provides functionality for manipulating @FilePath@ values, and is shipped with both <https://www.haskell.org/ghc/ GHC> and the <https://www.haskell.org/platform/ Haskell Platform>. It provides three modules:     .@@ -48,7 +48,7 @@         System.FilePath.Windows      build-depends:-        base >= 4 && < 4.10+        base >= 4 && < 4.11      ghc-options: -Wall