Program won't go away!

2000-10-18 Thread George Russell
In the GHC document, section "GHC-specific concurrency issues", it says: In a standalone GHC program, only the main thread is required to terminate in order for the process to terminate. I have a program (which does some fairly complex things with forking processes, calling sockets etcetera)

Re: Program won't go away!

2000-10-18 Thread Marcin 'Qrczak' Kowalczyk
Wed, 18 Oct 2000 16:32:21 +0200, George Russell [EMAIL PROTECTED] pisze: In a standalone GHC program, only the main thread is required to terminate in order for the process to terminate. I have a program (which does some fairly complex things with forking processes, The above fact

GHC for RedHat 7.0 (gcc 2.96)

2000-10-18 Thread Manuel M. T. Chakravarty
GHC (4.08.1) rpm packages for RedHat 7.0 are available from ftp://ftp.cse.unsw.edu.au/pub/users/chak/jibunmaki/i386/ghc-4.08.1-2.i386.rpm ftp://ftp.cse.unsw.edu.au/pub/users/chak/jibunmaki/i386/ghc-prof-4.08.1-2.i386.rpm [The second package is only required for profiling.] The

Socket.hs problem under Windows 2000

2000-10-18 Thread Martijn
Hi, I'm trying to set up some socket connections with Haskell on a Windows 2000 platform, but I can't seem to get them working. My program is rather simple: -- import Socket main = do { socket - listenOn (PortNumber 1234) ; return () } -- I know this shouldn't do

RE: Socket.hs problem under Windows 2000

2000-10-18 Thread Sigbjorn Finne
You need to init WinSock first, i.e., main = withSocketsDo $ do {...} --sigbjorn Martijn [mailto:[EMAIL PROTECTED]] writes: Hi, I'm trying to set up some socket connections with Haskell on a Windows 2000 platform, but I can't seem to get them working. My program is rather

Num class

2000-10-18 Thread Koen Claessen
Hi all, For years I have wondered why the Num class has the Eq class and the Show class as super classes. Because of this, I cannot make functions an instance of Num (becuase they are not in Eq or Show). Or a datatype respresenting an infinite amount of digits (because Eq would not make any

pronunciation of =

2000-10-18 Thread Scott Turner
Is there a common way to pronounce "=" in discussions or when teaching? I've learned all my Haskell from printed/visual documents. -- Scott Turner [EMAIL PROTECTED] http://www.ma.ultranet.com/~pkturner ___ Haskell mailing list [EMAIL PROTECTED]

Re: pronunciation of =

2000-10-18 Thread Lars Lundgren
On Wed, 18 Oct 2000, Scott Turner wrote: Is there a common way to pronounce "=" in discussions or when teaching? I've learned all my Haskell from printed/visual documents. How about 'bind'? and "" = 'then'. /Lars L ___ Haskell mailing list

Re: Num class

2000-10-18 Thread Marcin 'Qrczak' Kowalczyk
Wed, 18 Oct 2000 12:57:56 +0200 (MET DST), Koen Claessen [EMAIL PROTECTED] pisze: The defaulting mechanism works as follows: If there is an unresolved overloading error on a type variable a, which has as an *only* constraint (Num a), then we take a to be the suitable default. This is not

RE: Num class

2000-10-18 Thread Mark P Jones
Hi Koen, | If Show were not a super class of Num, the following program | would generate an error: | | main = print 42 | | If Eq were not a super class, the following program would | not work: | | main = print (if 42 == 42 then "koe" else "apa") | | These programs are all fixed by

mapM/concatMapM

2000-10-18 Thread Sengan Baring-Gould
mapM seems to be a memory hog (and thus also concatMapM). In the following eg: main = mapM print ([1..102400] :: [Integer]) memory usage climbs to 1.6M with ghc and needs -K20M, whereas with main = print ([1..102400] :: [Integer]) memory usage is only 1300 bytes. I instrumented mapM:

Re: mapM/concatMapM

2000-10-18 Thread Joe English
[EMAIL PROTECTED] (Sengan Baring-Gould) wrote: mapM seems to be a memory hog (and thus also concatMapM). In the following eg: main = mapM print ([1..102400] :: [Integer]) memory usage climbs to 1.6M with ghc and needs -K20M As a guess: since 'mapM print ([1..102400] :: [Integer])' has

Re: mapM/concatMapMy

2000-10-18 Thread Sengan Baring-Gould
[EMAIL PROTECTED] (Sengan Baring-Gould) wrote: mapM seems to be a memory hog (and thus also concatMapM). In the following eg: main = mapM print ([1..102400] :: [Integer]) memory usage climbs to 1.6M with ghc and needs -K20M As a guess: since 'mapM print ([1..102400] ::

Re: mapM/concatMapMy

2000-10-18 Thread Sengan Baring-Gould
[EMAIL PROTECTED] (Sengan Baring-Gould) wrote: mapM seems to be a memory hog (and thus also concatMapM). In the following eg: main = mapM print ([1..102400] :: [Integer]) memory usage climbs to 1.6M with ghc and needs -K20M As a guess: since 'mapM print ([1..102400]