RE: [Haskell] reasons for non-portability

2004-03-22 Thread Simon Marlow
> Thanks for the info. > > Well, according to that explanation, all modules would be > non-portable since > the Prelude is normally implemented using non-standard > features. I think, > this is solved by declaring all modules described in the > Haskell 98 Report > portable. > > One quest

Re: [Haskell] reasons for non-portability

2004-03-22 Thread Wolfgang Jeltsch
Am Montag, 22. März 2004 13:29 schrieben Sie: > On Sat, Mar 20, 2004 at 08:50:10PM +0100, Wolfgang Jeltsch wrote: > > according to > > http://www.haskell.org/hierarchical-modules/libraries/ > > reference-libraries.html#MODULE-HEADER, > > each module should have a header which contains a lin

Re: [Haskell] reasons for non-portability

2004-03-22 Thread Wolfgang Jeltsch
Am Montag, 22. März 2004 12:46 schrieben Sie: > > Am Sonntag, 21. März 2004 12:36 schrieben Sie: > > > 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

Re: [Haskell] reasons for non-portability

2004-03-22 Thread Keith Wansbrough
> Am Sonntag, 21. März 2004 12:36 schrieben Sie: > > 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. > >

Re: [Haskell] reasons for non-portability

2004-03-21 Thread Wolfgang Jeltsch
Am Sonntag, 21. März 2004 12:36 schrieben Sie: > 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, othe

Re: [Haskell] reasons for non-portability

2004-03-21 Thread 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. Th

[Haskell] reasons for non-portability

2004-03-20 Thread Wolfgang Jeltsch
Hello, according to http://www.haskell.org/hierarchical-modules/libraries/ reference-libraries.html#MODULE-HEADER, each module should have a header which contains a line about portability. My question is, if a module is considered non-portable only if it contains non-portable constructs