RE: [Haskell] COM port IO on a Windows machine?

Thanks, Steve and Axel, for your help. I have got serial port IO working, but the solution is a bit ugly. My solution (below) works on Windows 2000, Hugs Nov 2003. It does not work with Windows 2000, GHI 5.04.2. Later tonight I will try it on Windows ME with the latest versions of GHC and Hugs. Th

Re: [Haskell] ANNOUNCE: GHC version 6.2.1

On Monday 22 March 2004 16:40, Simon Marlow wrote: > > - The "threaded runtime system" is included by default. To link > a program with this variant of the RTS, add the -threaded option > when linking. After downloaded the sources i found that ./configure --help still lists the -threa

Re: [Haskell] main::[String]->IO() ?

Steffen Mazanek <[EMAIL PROTECTED]> writes: > Hello everybody, > > each time I write an application that makes use of command line arguments > I have to copy&paste the code for dealing with these args to my program > from a reference implementation, because it is so hard to remember. > What do yo

Re: [Haskell] main::[String]->IO() ?

I typically do: ... main = getArgs >>= go go [whatever] = ... On Mon, 22 Mar 2004, Steffen Mazanek wrote: > Hello everybody, > > each time I write an application that makes use of command line arguments > I have to copy&paste the code for dealing with these args to my program > from a referen

[Haskell] main::[String]->IO() ?

Hello everybody, each time I write an application that makes use of command line arguments I have to copy&paste the code for dealing with these args to my program from a reference implementation, because it is so hard to remember. What do you think about changing the default type of main or provi

Re: [Haskell] Proposal for a Standard of Abstract Collections (with Reference Implementation)

Another comment is that it looks too complicated. Your basic Collection class has 30 members, and some of them are clearly excessive: do you really need all of has, elem, (#), not_elem, and (/#) in the class (rather than defined as auxiliary functions, possibly optimised with fusion)? (Of course,

RE: [Haskell] reasons for non-portability

> 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] GHC binary for Cygwin

> The other day, I tried to compile the Fudgets library with > GHC-MinGW. It > didn't work, of course, and having GHC for Cygwin would presumably > significantly reduce the amount of pain required to port it. (Support > for certain Posix system calls and symbolic links would be helpful.) > >

[Haskell] ANNOUNCE: GHC version 6.2.1

The (Interactive) Glasgow Haskell Compiler -- version 6.2.1 We are pleased to announce a new patchlevel release of the Glasgow Haskell Compiler (GHC), version 6.2.1.

Re: [Haskell] reasons for non-portability

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

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

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