[Haskell] reasons for non-portability

Sven Panne Sven.Panne at aedion.de
Sun Mar 21 12:36:29 EST 2004

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.:



More information about the Haskell mailing list