External Core front-end in GHC 5.03

2002-05-03 Thread Kirsten Chevalier
Hi, I just downloaded and built the latest version of GHC from the CVS repository yesterday and tried to use it to compile an external Core file, which caused the compiler to crash: $ ghc -fext-core -fno-code hello.hs $ ghc hello.hcr Segmentation fault I know that the external Core feature is

infix type constructors

2002-05-03 Thread Okasaki, C. DR EECS
I'm not sure how long this has been implemented in GHC, but I just noticed that infix type constructors are allowed, as in data a :- b = ... The syntactic asymmetry between type constructors and data contructors has bothered me for a while, so this is a welcome change! However, this syntax

What's the '0' for in the version number?

2002-05-03 Thread Ashley Yakeley
Why is it GHC 5.02.2, 5.03 etc.? Wouldn't it be easier with 5.2.2, 5.3? -- Ashley Yakeley, Seattle WA ___ Glasgow-haskell-users mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/glasgow-haskell-users

SAS'02 -- DEADLINE EXTENSION -- MAY 10

2002-05-03 Thread SAS2002
(Apologies for multiple postings) Due to numerous requests, the submission deadline for SAS'02 has been extended to:**Friday MAY 10** -- CALL FOR PAPERS (SAS'02)

tricky instance declarations

2002-05-03 Thread Warrick Gray
Hi all, I'm not very current on the latest wonders of haskell typing, but I feel that something like the following should be possible: data ConnError = ... -- error propagating monad: instance Monad (Either ConnError) where (Left e) = _ = Left e (Right v) = f = f v return = Right

Re: tricky instance declarations

2002-05-03 Thread Alastair Reid
Warrick Gray [EMAIL PROTECTED] writes: data ConnError = ... -- error propagating monad: instance Monad (Either ConnError) where -- combined IO error propagating monads instance Monad (IO (Either ConnError a)) where I know the first declaration works with GHC compiler flag

CFP: JFP Special Issue on Functional Pearls

2002-05-03 Thread Ralf Hinze
Apologies if you receive multiple copies... CALL FOR PAPERS Special Issue on Functional Pearls http://www.informatik.uni-bonn.de/~ralf/necklace.html

Syntax highlighting for KDE's Kate

2002-05-03 Thread Ralf Hinze
Dear KDE users, I've hacked syntax highlighting files for Kate, KDE's editor. Feel free to use or to modify them. http://www.informatik.uni-bonn.de/~ralf/software.html#syntax Cheers, Ralf ___ Haskell mailing list [EMAIL PROTECTED]

duplicate instance declarations

2002-05-03 Thread Hal Daume III
Why is this a duplicate instance declaration: class C a class D b data T a b instance (C (T a b), C a) = D b instance (C (T a b), C b) = D a These are symmetric, but not duplicate, as I see it. -- Hal Daume III Computer science is no more about computers| [EMAIL PROTECTED] than

Re: duplicate instance declarations

2002-05-03 Thread C T McBride
Hi Why is this a duplicate instance declaration: class C a class D b data T a b instance (C (T a b), C a) = D b instance (C (T a b), C b) = D a These are symmetric, but not duplicate, as I see it. Suppose we add instance C () instance C (T () ()) Now there are two ways to

Re: Syntax highlighting for KDE's Kate

2002-05-03 Thread Brian Huffman
On Friday 03 May 2002 06:29 am, Ralf Hinze wrote: Dear KDE users, I've hacked syntax highlighting files for Kate, KDE's editor. Feel free to use or to modify them. http://www.informatik.uni-bonn.de/~ralf/software.html#syntax Cheers, Ralf Attached here is another syntax highlighting

Deforestration harmful?

2002-05-03 Thread Shin-Cheng Mu
Hi all, We encountered a case where elimination of intermediate data structure seeems to have a bad impact on the overall performance and we were wondering why. Relationally, our program would be as simple as: f . g where g :: Seed - Tree1 and f :: Tree1 - Tree2. Basically g generate

Re: ANNOUNCE: Haddock version 0.1, a Haskell documentation tool

2002-05-03 Thread Ashley Yakeley
At 2002-05-01 04:48, Simon Marlow wrote: I'm pleased to announce version 0.1 of Haddock, a documentation generation tool for Haskell source code. I take it this is the standard Haskell documentation tool now, that implementations of the standard libraries will use? I've been waiting for