[Haskell] reasons for non-portability

[Sven Panne]

Wolfgang Jeltsch wrote:
> [...] My question is, if a module is considered non-portable only if it
> contains non-portable constructs itself, or if a module is also non-portable
> if it just imports a module which is non-portable.

Both, otherwise stating the property "portable" wouldn't help very much.
There are already a few examples in the hierarchical libraries, e.g.:

    http://cvs.haskell.org/cgi-bin/cvsweb.cgi/fptools/libraries/base/Data/STRef.hs?rev=1.12&content-type=text/x-cvsweb-markup
    http://cvs.haskell.org/cgi-bin/cvsweb.cgi/fptools/libraries/base/Text/Read/Lex.hs?rev=1.15&content-type=text/x-cvsweb-markup

Cheers,
    S.