config.h namespace clashes

2004-03-01 Thread John Meacham
The inclusion of the GHC made config.h in HsFFI.h makes it extremely
difficult to use autoconf with ones own projects without dealing with
horrible name clashes everywhere. Is there some way this can be fixed?
perhaps pre-generating the HsFFI.h.

although I don't think it is stated explicitly by the FFI report, I would
assume that HsFFI.h should not clash with anything that doesn't start
with Hs, hs_ or HS_.

also, it would be good if config.h could be renamed to something like
ghc-config.h, because otherwise the conflict between the names can hide
bugs where you get the incorrect config.h or make it tricky to get at
the GHC one if it is actually the one you want.
John

-- 
---
John Meacham - California Institute of Technology, Alum. - [EMAIL PROTECTED]
---
___
Glasgow-haskell-users mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


Happy Question

2004-03-01 Thread Ashley Yakeley
My hand-written S-expression parser for HScheme is very very slow. 
Really quite a bit slower than it ought to be. So I'd like to switch to 
Happy instead.

The problem is my parser should be monadic, but the monad type is 
generalised (basically of the form (context m) = m). Is there a way of 
switching on monadic-ness, so I can have a monadic happyError, but 
without giving type signatures to happyThen and happyReturn? Or else 
allowing a class context for the type signatures?

-- 
Ashley Yakeley, Seattle WA

___
Glasgow-haskell-users mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


RE: Generics... no Tuples 2 either...

2004-03-01 Thread Simon Peyton-Jones
Tuples and Double are there in the HEAD build now -- but we're still
thinking about how best to treat Ptr, which is essentially
un-marshalable.

| -Original Message-
| From: [EMAIL PROTECTED]
[mailto:glasgow-haskell-users-
| [EMAIL PROTECTED] On Behalf Of MR K P SCHUPKE
| Sent: 26 February 2004 18:33
| To: [EMAIL PROTECTED]
| Subject: Generics... no Tuples  2 either...
| 
| 
| Any chance of Data instances for tuples of size
| greater than 2... One of the nice things about generics is
| you can use them by deriving Data on your datatypes - of
| course this doesn't work if you all of a sudden have to
| put a load of boiler-plate in just to use tuples...
| 
|   Regards,
|   Keean Schupke
| ___
| Glasgow-haskell-users mailing list
| [EMAIL PROTECTED]
| http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
___
Glasgow-haskell-users mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


RE: config.h namespace clashes

2004-03-01 Thread Simon Marlow
 
 The inclusion of the GHC made config.h in HsFFI.h makes it extremely
 difficult to use autoconf with ones own projects without dealing with
 horrible name clashes everywhere. Is there some way this can be fixed?
 perhaps pre-generating the HsFFI.h.
 
 although I don't think it is stated explicitly by the FFI 
 report, I would
 assume that HsFFI.h should not clash with anything that doesn't start
 with Hs, hs_ or HS_.
 
 also, it would be good if config.h could be renamed to something like
 ghc-config.h, because otherwise the conflict between the 
 names can hide
 bugs where you get the incorrect config.h or make it tricky to get at
 the GHC one if it is actually the one you want.

Yes, we should definitely do that.  I'm surprised this hasn't caused
problems before (or maybe it has?).

Cheers,
Simon
___
Glasgow-haskell-users mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users


Re: config.h namespace clashes

2004-03-01 Thread John Meacham
On Mon, Mar 01, 2004 at 11:55:05AM -, Simon Marlow wrote:
 Yes, we should definitely do that.  I'm surprised this hasn't caused
 problems before (or maybe it has?).

The reasons it has not been as much of an issue before are twofold as
far as I can tell, 

1. cpp only complains if you #define something to a different value than
it was previously defined. chances are any autoconf tests will succeed
similarly during the building of ghc and later. 

2. autoconf only recently started #defining PACKAGE, VERSION, BUGREPORT
and friends, which will almost definatly be different. 

so, they probably were conflicting a lot before, but the symtoms were
hidden. At least that was what I determined from my post-mortem when
figuring out why the compiler started horking on -Werrors with ghc 6.2.
John



-- 
---
John Meacham - California Institute of Technology, Alum. - [EMAIL PROTECTED]
---
___
Glasgow-haskell-users mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users