- Glasgow-haskell-users

RE: Strange fatal error
by Julian Seward (Intl Vendor) 19 Nov '01

19 Nov '01

We fixed some obscure GC-related bugs in 5.02. The fixes are in 5.02.1. When you try it with 5.02.1, does the problem still happen? J -----Original Message----- From: Andre W B Furtado [mailto:awfurtado@uol.com.br] Sent: Tuesday, November 13, 2001 7:41 PM To: glasgow-haskell-users(a)haskell.org Cc: hopengl(a)haskell.org Subject: Strange fatal error Can anyone explain me the following error? fatal error: scavenge: unimplemented/strange closure type 0 @ 08C03FD0 (this happened with a program that reads and do some manipulations in a 3MB bitmap file, using HOpenGL-1.01 and GHC-5.02 under Windows 98 + Cygwin) Thanks, -- Andre

2 1

GHC-5.02(.1) InstallShield for Windows
by Andre W B Furtado 18 Nov '01

18 Nov '01

I just would like to report that, if you have GHC-5.02 installed and want to install GHC-5.02.1 (under Windows), you'll need to uninstall GHC-5.02 first, otherwise the InstallShield for GHC-5.02.1 won't work as expected. Is this a bug? -- Andre

1 0

ghc-5.02 refuses to open a device file
by Max A . K . 16 Nov '01

16 Nov '01

I guess it's a [mis]feature, since 5.00 worked, but can hardly imagine anybody could need it. ======= Prelude> h<-IO.openFile "/dev/zero" IO.ReadMode *** Exception: unsupported operation Action: openFile Reason: unknown file type File: /dev/rtf0 Prelude> Leaving GHCi. max@max$cat /dev/zero <C-C> ======= Max.

1 0

FreeBSD/x86 package of 5.02.1 available
by Simon Marlow 15 Nov '01

15 Nov '01

FreeBSD/x86 packages of 5.02.1 are up on haskell.org. There's a native package: http://www.haskell.org/ghc/dist/5.02.1/ghc-5.02.1.tgz the port it was built from http://www.haskell.org/ghc/dist/5.02.1/ghc-5.02.1-i386-unknown-freebsd-p ort.tar.gz and a standard .tar.gz package http://www.haskell.org/ghc/dist/5.02.1/ghc-5.02.1-i386-unknown-freebsd.t ar.gz Cheers, Simon

1 0

RE: ghc --make + #include directories
by Simon Marlow 14 Nov '01

14 Nov '01

> Simon Marlow wrote: > > > What's wrong with just saying -I<dir> whenever you say -i<dir>? > > This seems to work but for more complicated combinations the > two options have slightly > different formats. For example, if I have several > directories separated by colons, and > end the list with a superfluous colon (which arises naturally > enough when the path is > auto-computed) I get messages like: Ok, that's a bug. In the meantime, you'll have to remove the trailing colon. Cheers, Simon

1 0

RE: ghc --make + #include directories
by Simon Marlow 14 Nov '01

14 Nov '01

> Thanks to ghc --make it is now common to compile files from a > different directory. > This creates a new problem, in that if a file starts with a > {-# include <c-header.h> #-} > directive, ghc will try to find c-header.h in the current > directory, not in the directory > containing the source file. So we need a way of changing the > gcc include path during > compilation of .hc files to include the directory containing > the source file. What's wrong with just saying -I<dir> whenever you say -i<dir>? Cheers, Simon

2 1

ghc --make + #include directories
by George Russell 14 Nov '01

14 Nov '01

Thanks to ghc --make it is now common to compile files from a different directory. This creates a new problem, in that if a file starts with a {-# include <c-header.h> #-} directive, ghc will try to find c-header.h in the current directory, not in the directory containing the source file. So we need a way of changing the gcc include path during compilation of .hc files to include the directory containing the source file.

1 0

RE: Input Processing Loops in Haskell
by Simon Marlow 14 Nov '01

14 Nov '01

> On Tue, Nov 13, 2001 at 05:02:54PM -0000, Simon Marlow wrote: > > > > You can paraphrase this in Haskell, in the IO monad, like this: > > > > loop = do { > > a <- get_input; > > if (a == gET_OUT) then return () else loop; > > } > > > I follow, but I've never seen brackets used in Haskell code. Are they > included for clarity, or do they have syntactic value? Is > this the same > as > > loop = do > a <- get_input > if (a == GET_OUT) then return () else loop > > ? Yes, it's the same. Some people prefer to use the explicit punctuation; personally I use whatever looks more readable for the code I'm writing, which in most cases means I use layout for small functions but punctuation for large chunks of code where it's hard to see which bits line up. Cheers, Simon

1 0

ANNOUNCE: linkchk-0.02 released
by Jens-Ulrik Petersen 14 Nov '01

14 Nov '01

Happy to announce linkchk version 0.02 is out. >From the NEWS file: * width of window is now fixed * new options to set: ** window width ** host to be pinged ** interface * checks ifconfig to see if interface is up * use implicit parameters for command-line options The tarball and i386 rpm are now available on: http://www.01.246.ne.jp/~juhp/haskell/linkchk/ linkchk is also on freshmeat.net. Enjoy, Jens

1 0

Strange fatal error
by Andre W B Furtado 13 Nov '01

13 Nov '01

Can anyone explain me the following error? fatal error: scavenge: unimplemented/strange closure type 0 @ 08C03FD0 (this happened with a program that reads and do some manipulations in a 3MB bitmap file, using HOpenGL-1.01 and GHC-5.02 under Windows 98 + Cygwin) Thanks, -- Andre

1 0