Aha! a partial fix! now everything works as expected.
I just needed to create a link from
libgmp.so.3 -> libgmp.so
and now it all works!
So the complete instructions for getting ghc working on a fedora 2
x86_64 system are
; yum install gmp.i386 readline.i386
; ln -s /usr/lib/libgmp.so.3 /usr/l
So my AMD64 books have been burning a hole in my bookshelf for so long,
I finally went out and got a athlon 64 and installed fedora core 2. much
to my dismay, ghc does not seem to work out of the box.
I took the following steps.
; yum install gmp.i386 readline.i386
now a
rpm -U
of the ghc rpms
Yes, I could quite easily write the generator in TemplateHaskell (have
played with it before)
_but_ I don't like the $(xxx) syntax... Perhaps if Simon could be
persuaded to allow deriving
clauses to be defined in TH?
data X x = X x
$(deriveMyClass (reify X))
could perhaps be defined from
data X
On 13/10/2004, at 10:02 AM, MR K P SCHUPKE wrote:
Okay, I see the Generic type class stuff does not support multi
parameter type classes. I guess I am stuck - any suggestions as to
how best do this?
I wish to be able to derive type level labels for datatypes, like
the following:
data Fred a = Fred
>look at the user manual.
Okay, I see the Generic type class stuff does not support multi
parameter type classes. I guess I am stuck - any suggestions as to
how best do this?
I wish to be able to derive type level labels for datatypes, like
the following:
data Fred a = Fred a deriving TTypea
Hi Simon!
On Wed, Oct 13, 2004 at 01:21:26PM +0100, Simon Peyton-Jones wrote:
> Two fixes suggest themselves
>
> 1. Separate 'deriving' from the data type decl, so you can say
> derive( Data TA, Typeable TA )
> anywhere. People sometimes ask for this for other reasons.
Good thing. Plu
(I assume you mean GHC.)
Don't look at the compiler, look at the user manual. That describes
what's supported. I have no current plans to withdraw any of the
current support.
Simon
| -Original Message-
| From: [EMAIL PROTECTED]
[mailto:glasgow-haskell-users-
| [EMAIL PROTECTED] On Beha
What is the situation with deriving?
Some instances can be derived automatically for both data/newtype (built in)?
Some instances cen be derived automatically for newtype (any)?
You used to be able to define functions useing {|+|} and {|*|} (or similar)
that could be derived for both data and n
On Wed, 13 Oct 2004 13:21:26 +0100, Simon Peyton-Jones
<[EMAIL PROTECTED]> wrote:
> 1. Separate 'deriving' from the data type decl, so you can say
> derive( Data TA, Typeable TA )
> anywhere. People sometimes ask for this for other reasons.
>
> 2. Allow instances in hi-boot files
>
> Y
| If I have two modules which are mutually recursive;
|
| module A where
| import B
| data TA = TA TB deriving (Data, Typeable)
|
| module B where
| import A
| data TB = TB TA deriving (Data, Typeable)
|
| How do I go about writing a hi-boot that will work in GHC?
Good question. At the moment
On 12 October 2004 18:06, Peter Simons wrote:
> is it possible that GHC doesn't process the -hidir and -odir
> command-line options correctly when -ddump-minimal-imports
> is given as well? I have had this problem right now and
> removing the -(hi|o)dir flags fixed it, so I figured I'd
> better sa
11 matches
Mail list logo