Re: Haskell-JNI Bridge

2001-07-05 Thread Antony Courtney
Hi, Ashley Yakeley wrote: > > Is Lambada (the Haskell-JNI bridge) gone? The web-page has disappeared. > Using Java seems by far the most obvious way of getting all that > GUI/network/SQL/whatever functionality, especially as the Java platform > is almost ubiquitous (unlike .NET, Tk, X, GTK+, Win

Re: infelicity in module imports

2001-07-05 Thread Malcolm Wallace
> In short, an import *always* brings the entire *qualified* set > of names into scope. Hiding and revealing applies only to > unqualified names. I agree with SimonM that this is not what the Report says. At one time it may have done, but careful reading shows that only the qualified names for

Re: infelicity in module imports

2001-07-05 Thread Chris Webb
"Simon Marlow" <[EMAIL PROTECTED]> writes: > Simon Peyton Jones writes: > > > In short, an import *always* brings the entire *qualified* set of > > names into scope. Hiding and revealing applies only to unqualified > > names. I must say that I thought GHC implemented this rule; if not I > > shou

Re: Haskell-JNI Bridge

2001-07-05 Thread C.Ryder
> Is Lambada (the Haskell-JNI bridge) gone? The web-page has disappeared. > Using Java seems by far the most obvious way of getting all that > GUI/network/SQL/whatever functionality, especially as the Java platform > is almost ubiquitous (unlike .NET, Tk, X, GTK+, Win32 GDI, etc.). I don't thi

RE: infelicity in module imports

2001-07-05 Thread Simon Marlow
Simon Peyton Jones writes: > In short, an import *always* brings the entire *qualified* > set of names into scope. Hiding and revealing applies only > to unqualified names. I must say that I thought GHC implemented > this rule; if not I should fix it. That's not my reading of the report, and i

Haskell-JNI Bridge

2001-07-05 Thread Ashley Yakeley
Is Lambada (the Haskell-JNI bridge) gone? The web-page has disappeared. Using Java seems by far the most obvious way of getting all that GUI/network/SQL/whatever functionality, especially as the Java platform is almost ubiquitous (unlike .NET, Tk, X, GTK+, Win32 GDI, etc.). In this apparent ab

RE: infelicity in module imports

2001-07-05 Thread Simon Peyton-Jones
| | > Currently, you are permitted to write | | > | | > import A hiding (f) | | > import B as A (f) | | > | | > and this means that everything exported from module A is visible, | | > with the exception that function `f' is overridden by a different | | > definition from module B. Her