Skip to content
  • randen's avatar
    d510c457
    The Haddock part for fully gcc-like response files · d510c457
    randen authored
    " driver/Main.hs
      * Moved the response file handling into ResponseFile.hs,
        updating import section as appropriate.
    * driver/ResponseFile.hs
      * New file. In anticipation that maybe some day this could
        be provided by another library, and to make it possible
        to unit test, this functionality is pulled out of the
        Main.hs module, and expanded to support the style/format
        of response files which gcc uses.
      * The specification for the format of response files which
        gcc generates and consumes, seems to be best derived from
        the gcc code itself (libiberty/argv.c), so that is what
        has been done here.
      * This is intended to fix haskell/haddock#379
    * driver-test/Main.hs
      * New file for testing code in the driver source tree
    * driver-test/ResponseFileSpec.hs
      * Tests, adapted/adopted from the same gcc code where the
        escaping/unescaping is from, in the hspec style of unit
        tests
    * haddock.cabal
      * Add the driver-test test-suite.  Introduces a new library
        dependency (upon hspec) for the haddock driver target in
        the haddock.cabal file, but practically, this should not
        be a problem as the haddock-api tests already depend on
        hspec.
    d510c457
    The Haddock part for fully gcc-like response files
    randen authored
    " driver/Main.hs
      * Moved the response file handling into ResponseFile.hs,
        updating import section as appropriate.
    * driver/ResponseFile.hs
      * New file. In anticipation that maybe some day this could
        be provided by another library, and to make it possible
        to unit test, this functionality is pulled out of the
        Main.hs module, and expanded to support the style/format
        of response files which gcc uses.
      * The specification for the format of response files which
        gcc generates and consumes, seems to be best derived from
        the gcc code itself (libiberty/argv.c), so that is what
        has been done here.
      * This is intended to fix haskell/haddock#379
    * driver-test/Main.hs
      * New file for testing code in the driver source tree
    * driver-test/ResponseFileSpec.hs
      * Tests, adapted/adopted from the same gcc code where the
        escaping/unescaping is from, in the hspec style of unit
        tests
    * haddock.cabal
      * Add the driver-test test-suite.  Introduces a new library
        dependency (upon hspec) for the haddock driver target in
        the haddock.cabal file, but practically, this should not
        be a problem as the haddock-api tests already depend on
        hspec.
Loading