diff options
author | randen <randen@users.noreply.github.com> | 2016-01-01 18:02:11 -0800 |
---|---|---|
committer | randen <randen@users.noreply.github.com> | 2016-01-01 23:45:25 -0800 |
commit | d510c45790432249fe7027b1ed70ce1c06fdd824 (patch) | |
tree | f7a276c6cd870aa903abf4f960269e03e3d9be31 /haddock-library/vendor/attoparsec-0.12.1.1/Data/Attoparsec/ByteString.hs | |
parent | ac10a4ccbe416e8612c6ca49b9f19c3a6f4cf25f (diff) |
The Haddock part for fully gcc-like response files
" 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.
Diffstat (limited to 'haddock-library/vendor/attoparsec-0.12.1.1/Data/Attoparsec/ByteString.hs')
0 files changed, 0 insertions, 0 deletions