1. 28 Nov, 2019 1 commit
  2. 13 Sep, 2019 1 commit
  3. 16 Dec, 2014 1 commit
  4. 24 Sep, 2014 1 commit
  5. 18 Sep, 2014 1 commit
  6. 22 Sep, 2013 1 commit
  7. 17 Sep, 2013 2 commits
  8. 17 Feb, 2013 1 commit
  9. 15 Feb, 2013 1 commit
  10. 27 Oct, 2012 1 commit
    • ian@well-typed.com's avatar
      Remove commented types in module export lists · fda30027
      ian@well-typed.com authored
      These comments are rather less useful now that haddock can give docs
      with the same informatino in the module synopsis.
      Having to maintain them when making changes to the library is a pain,
      and when people forget about doing so there is nothing that checks that
      the comments are right, so mistakes tend to linger.
      Of the comments that my script detected, 78 of 684 were already
      incorrect in one way or another, e.g. missing context:
          Comment type: Int -> a -> ShowS
          Actual type:  Show a => Int -> a -> ShowS
      wrong context:
          Comment type: Integral a => a -> (Char -> Bool) -> (Char -> Int) -> ReadS a
          Actual type:  Num a => a -> (Char -> Bool) -> (Char -> Int) -> ReadS a
      not following a class change (e.g. Num losing its Eq superclass):
          Comment type: Num a => ReadP a
          Actual type:  (Eq a, Num a) => ReadP a
      not following the Exceptions change:
          Comment type: Exception -> IO ()
          Actual type:  SomeException -> IO ()
      or just always been wrong:
          Comment type: StablePtr a -> a
          Actual type:  StablePtr a -> IO a
  11. 19 Jun, 2012 1 commit
  12. 26 Oct, 2011 1 commit
  13. 18 Jun, 2011 1 commit
  14. 11 Feb, 2011 1 commit
  15. 05 Feb, 2011 1 commit
  16. 28 Jan, 2011 1 commit
  17. 28 Jul, 2010 1 commit
  18. 12 Jun, 2009 1 commit
    • Simon Marlow's avatar
      Rewrite of the IO library, including Unicode support · 7b067f2d
      Simon Marlow authored
      * Unicode support for Handle I/O:
        ** Automatic encoding and decoding using a per-Handle encoding.
        ** The encoding defaults to the locale encoding (only on Unix 
           so far, perhaps Windows later).
        ** Built-in UTF-8, UTF-16 (BE/LE), and UTF-32 (BE/LE) codecs.
        ** iconv-based codec for other encodings on Unix
      * Modularity: the low-level IO interface is exposed as a type class
        (GHC.IO.IODevice) so you can build your own low-level IO providers and
        make Handles from them.
      * Newline translation: instead of being Windows-specific wired-in
        magic, the translation from \r\n -> \n and back again is available
        on all platforms and is configurable for reading/writing
      Unicode-aware Handles
      This is a significant restructuring of the Handle implementation with
      the primary goal of supporting Unicode character encodings.
      The only change to the existing behaviour is that by default, text IO
      is done in the prevailing locale encoding of the system (except on
      Windows [1]).  
      Handles created by openBinaryFile use the Latin-1 encoding, as do
      Handles placed in binary mode using hSetBinaryMode.
      We provide a way to change the encoding for an existing Handle:
         GHC.IO.Handle.hSetEncoding :: Handle -> TextEncoding -> IO ()
      and various encodings (from GHC.IO.Encoding):
         utf16, utf16le, utf16be,
         utf32, utf32le, utf32be,
      and a way to lookup other encodings:
         GHC.IO.Encoding.mkTextEncoding :: String -> IO TextEncoding
      (it's system-dependent whether the requested encoding will be
      We may want to export these from somewhere more permanent; that's a
      topic for a future library proposal.
      Thanks to suggestions from Duncan Coutts, it's possible to call
      hSetEncoding even on buffered read Handles, and the right thing
      happens.  So we can read from text streams that include multiple
      encodings, such as an HTTP response or email message, without having
      to turn buffering off (though there is a penalty for switching
      encodings on a buffered Handle, as the IO system has to do some
      re-decoding to figure out where it should start reading from again).
      If there is a decoding error, it is reported when an attempt is made
      to read the offending character from the Handle, as you would expect.
      Performance varies.  For "hGetContents >>= putStr" I found the new
      library was faster on my x86_64 machine, but slower on an x86.  On the
      whole I'd expect things to be a bit slower due to the extra
      decoding/encoding, but probabaly not noticeably.  If performance is
      critical for your app, then you should be using bytestring and text
      [1] Note: locale encoding is not currently implemented on Windows due
      to the built-in Win32 APIs for encoding/decoding not being sufficient
      for our purposes.  Ask me for details.  Offers of help gratefully
      Newline Translation
      In the old IO library, text-mode Handles on Windows had automatic
      translation from \r\n -> \n on input, and the opposite on output.  It
      was implemented using the underlying CRT functions, which meant that
      there were certain odd restrictions, such as read/write text handles
      needing to be unbuffered, and seeking not working at all on text
      In the rewrite, newline translation is now implemented in the upper
      layers, as it needs to be since we have to perform Unicode decoding
      before newline translation.  This means that it is now available on
      all platforms, which can be quite handy for writing portable code.
      For now, I have left the behaviour as it was, namely \r\n -> \n on
      Windows, and no translation on Unix.  However, another reasonable
      default (similar to what Python does) would be to do \r\n -> \n on
      input, and convert to the platform-native representation (either \r\n
      or \n) on output.  This is called universalNewlineMode (below).
      The API is as follows.  (available from GHC.IO.Handle for now, again
      this is something we will probably want to try to get into System.IO
      at some point):
      -- | The representation of a newline in the external file or stream.
      data Newline = LF    -- ^ "\n"
                   | CRLF  -- ^ "\r\n"
                   deriving Eq
      -- | Specifies the translation, if any, of newline characters between
      -- internal Strings and the external file or stream.  Haskell Strings
      -- are assumed to represent newlines with the '\n' character; the
      -- newline mode specifies how to translate '\n' on output, and what to
      -- translate into '\n' on input.
      data NewlineMode 
        = NewlineMode { inputNL :: Newline,
                          -- ^ the representation of newlines on input
                        outputNL :: Newline
                          -- ^ the representation of newlines on output
                   deriving Eq
      -- | The native newline representation for the current platform
      nativeNewline :: Newline
      -- | Map "\r\n" into "\n" on input, and "\n" to the native newline
      -- represetnation on output.  This mode can be used on any platform, and
      -- works with text files using any newline convention.  The downside is
      -- that @readFile a >>= writeFile b@ might yield a different file.
      universalNewlineMode :: NewlineMode
      universalNewlineMode  = NewlineMode { inputNL  = CRLF, 
                                            outputNL = nativeNewline }
      -- | Use the native newline representation on both input and output
      nativeNewlineMode    :: NewlineMode
      nativeNewlineMode     = NewlineMode { inputNL  = nativeNewline, 
                                            outputNL = nativeNewline }
      -- | Do no newline translation at all.
      noNewlineTranslation :: NewlineMode
      noNewlineTranslation  = NewlineMode { inputNL  = LF, outputNL = LF }
      -- | Change the newline translation mode on the Handle.
      hSetNewlineMode :: Handle -> NewlineMode -> IO ()
      IO Devices
      The major change here is that the implementation of the Handle
      operations is separated from the underlying IO device, using type
      classes.  File descriptors are just one IO provider; I have also
      implemented memory-mapped files (good for random-access read/write)
      and a Handle that pipes output to a Chan (useful for testing code that
      writes to a Handle).  New kinds of Handle can be implemented outside
      the base package, for instance someone could write bytestringToHandle.
      A Handle is made using mkFileHandle:
      -- | makes a new 'Handle'
      mkFileHandle :: (IODevice dev, BufferedIO dev, Typeable dev)
                    => dev -- ^ the underlying IO device, which must support
                           -- 'IODevice', 'BufferedIO' and 'Typeable'
                    -> FilePath
                           -- ^ a string describing the 'Handle', e.g. the file
                           -- path for a file.  Used in error messages.
                    -> IOMode
                           -- ^ The mode in which the 'Handle' is to be used
                    -> Maybe TextEncoding
                           -- ^ text encoding to use, if any
                    -> NewlineMode
                           -- ^ newline translation mode
                    -> IO Handle
      This also means that someone can write a completely new IO
      implementation on Windows based on native Win32 HANDLEs, and
      distribute it as a separate package (I really hope somebody does
      This restructuring isn't as radical as previous designs.  I haven't
      made any attempt to make a separate binary I/O layer, for example
      (although hGetBuf/hPutBuf do bypass the text encoding and newline
      translation).  The main goal here was to get Unicode support in, and
      to allow others to experiment with making new kinds of Handle.  We
      could split up the layers further later.
      API changes and Module structure
      NB. GHC.IOBase and GHC.Handle are now DEPRECATED (they are still
      present, but are just re-exporting things from other modules now).
      For 6.12 we'll want to bump base to version 5 and add a base4-compat.
      For now I'm using #if __GLASGOW_HASKEL__ >= 611 to avoid deprecated
      I split modules into smaller parts in many places.  For example, we
      now have GHC.IORef, GHC.MVar and GHC.IOArray containing the
      implementations of IORef, MVar and IOArray respectively.  This was
      necessary for untangling dependencies, but it also makes things easier
      to follow.
      The new module structurue for the IO-relatied parts of the base
      package is:
         Implementation of the IO monad; unsafe*; throw/catch
         The IOMode type
         Buffers and operations on them
         The IODevice and RawIO classes.
         The BufferedIO class.
         The FD type, with instances of IODevice, RawIO and BufferedIO.
         IO-related Exceptions
         The TextEncoding type; built-in TextEncodings; mkTextEncoding
         Implementation internals for GHC.IO.Encoding
         The main API for GHC's Handle implementation, provides all the Handle
         operations + mkFileHandle + hSetEncoding.
         Implementation of Handles and operations.
         Parts of the Handle API implemented by file-descriptors: openFile,
         stdin, stdout, stderr, fdToHandle etc.
  19. 06 Feb, 2009 1 commit
  20. 14 Jan, 2009 1 commit
  21. 04 Jan, 2009 1 commit
  22. 12 Aug, 2008 1 commit
    • Ross Paterson's avatar
      split most of Control.Exception into new Control.Exception.Base · ec16083b
      Ross Paterson authored
      Move everything but catches/Handler into a new internal module.
      This was needed to get the new exceptions working with Hugs, because Hugs
      has the constraint that all Haskell 98 library modules, and everything
      they include, must be Haskell 98.  This also involves a different
      representation of SomeException for Hugs, so that type is exported
      opaquely for Hugs.  Then Control.Exception.Base is Haskell 98 as far as
      Hugs is concerned, but Control.Exception needs the extensions turned on.
      Control.Exception re-exports everything from Control.Exception.Base
      except the functions used by the GHC runtime.
  23. 04 Aug, 2008 1 commit
  24. 01 Aug, 2008 1 commit
  25. 30 Jul, 2008 1 commit
  26. 16 Jun, 2008 1 commit
  27. 08 Mar, 2008 1 commit
  28. 04 Mar, 2007 1 commit
  29. 11 Jan, 2005 1 commit
  30. 30 Aug, 2003 1 commit
  31. 27 May, 2003 1 commit
  32. 31 Mar, 2003 2 commits
  33. 08 Jan, 2003 2 commits
  34. 20 Dec, 2002 1 commit
    • ross's avatar
      [project @ 2002-12-20 17:56:21 by ross] · baf09e29
      ross authored
      Make Hugs use all of System.IO.Error.
      Also renamed the ioe_descr field of IOException (not part of the public
      interface) to ioe_description, matching Hugs.
  35. 12 Dec, 2002 1 commit
    • ross's avatar
      [project @ 2002-12-12 13:42:46 by ross] · 455d1bbd
      ross authored
      Changes to the exception interface, as discussed on the libraries list.
      1) Move bracket and bracket_ from GHC.Exception (and hence System.IO)
         to haskell98/IO.hs.  These two should now never be used (except in
         all-H98 programs), and this will save users of the new libraries from
         having to hide them.  Use the ones in Control.Exception instead.
      2) Define
              type IOError = IOException      -- was Exception
         leaving the type of Prelude.ioError as IOError -> IO a,
         but adding to Control.Exception
              throwIO :: Exception -> IO a
      The result is a type distinction between the variants of catch and try:
      	Prelude.catch           :: IO a -> (IOError -> IO a) -> IO a
      	Control.Exception.catch :: IO a -> (Exception -> IO a) -> IO a
      	System.IO.Error.try     :: IO a -> IO (Either IOError a)
      	Control.Exception.try   :: IO a -> IO (Either Exception a)
      These are breaking changes: the first one affects only import lists,
      but the second will bite in the following situations:
      - using ioError on general Exceptions: use throwIO instead.
      - using throw on IOErrors: if in the IO monad, use ioError instead.
        Otherwise, use throw (IOException e), but why are you throwing
        IO exceptions outside of the IO monad?
      Minor changes:
      - System.IO.Error now exports catch and try
      - moved try from GHC.Exception to System.IO.Error, because it's
        portable and can be shared by Hugs.
  36. 05 Dec, 2002 1 commit
  37. 09 Oct, 2002 1 commit