How do I use sockets in Haskell? The ghc manual had some information in the users
guide (6.7 Interfaces to C libraries) but the sentence which started tantalisingly
"Various examples of networking Haskell code are provided in "
had no second half.
I'd prefer to use hugs during development bu
I've taken a look at these. I'll limit myself to just one comment:
>1.1.1. Constructor names
>
>Empty values of type X have the name emptyX, e.g. emptySet.
You've struck a pet peeve of mine. These suffixes are doing namespace
management, avoiding name clashes between different things that
Hello,
is it possible to have class instances local to a module or a function?
This would be very useful since it occurs quite often that certain
instances are appropriate for most modules but one.
Michael
Chris Okasaki writes:
> >Empty values of type X have the name emptyX, e.g. emptySet.
>
> You've struck a pet peeve of mine. These suffixes are doing namespace
> management, avoiding name clashes between different things that you
> want to call empty. But Haskell already has a perfectly
You can't hide instances. It's sometimes nice to, but it
leads to complications that there seemed to be no
clean way to resolve. So the design is clean, but lacks a
desirable feature.
Simon
| -Original Message-
| From: Michael Marte [mailto:[EMAIL PROTECTED]]
| Sent: 23 June 2000 14:
Chris Okasaki wrote:
> I've taken a look at these. I'll limit myself to just one comment:
>
> >1.1.1. Constructor names
> >
> >Empty values of type X have the name emptyX, e.g. emptySet.
>
> You've struck a pet peeve of mine. These suffixes are doing namespace
> management, avoiding name cl
Frank Atanassow wrote:
> To be fair, I can give 4 arguments against it.
>
> 1) Hugs's error messages don't qualify names, so they become very difficult
> to read when you use this convention.
That's a totally bogus reason. Tell the implementors to fix Hugs.
> 2) The Prelude doesn't u
> "chris" == Chris Okasaki <[EMAIL PROTECTED]> writes:
chris> You've struck a pet peeve of mine. These suffixes are doing namespace
chris> management, avoiding name clashes between different things that you
chris> want to call empty. But Haskell already has a perfectly good language
chris>
Lennart Augustsson wrote:
> Frank Atanassow wrote:
> > 2) The Prelude doesn't use it.
>
> Well, it doesn't for historical reasons.
Am I alone in thinking that the prelude is desperately in
need of restructuring? Has anyone got any proposals for
nested modules (so we could have Prelude.List.
| 1) Hugs's error messages don't qualify names, so they become
| very difficult to read when you use this convention.
| ...
| ... #1 is the least important in theory, since it's fixable and
| implementation-dependent, but turned out for me to be the most
| important in practice; Hugs' atro
Fri, 23 Jun 2000 09:05:54 -0400 (EDT), Chris Okasaki <[EMAIL PROTECTED]> pisze:
> These suffixes are doing namespace management, avoiding name clashes
> between different things that you want to call empty. But Haskell
> already has a perfectly good language mechanism for doing this --
> the mod
On Fri, 23 Jun 2000, Mark P Jones wrote:
[snip]
> Hugs is also quite old; it's core goes back nearly ten years!
> With a more "modern" interface, we might solve the interface
> dilemma by arranging for fully qualified names, types, etc. to
> pop up in a "tooltip" when the user mouses over an id
23 Jun 2000 16:57:48 GMT, Marcin 'Qrczak' Kowalczyk <[EMAIL PROTECTED]> pisze:
> * [...]
* Overloading by the monad (like MArray) allows adding instances for
derived monads, without explicit lifting on each use.
--
__("< Marcin Kowalczyk * [EMAIL PROTECTED] http://qrczak.ids.net.pl/
\__/
> > These suffixes are doing namespace management, avoiding name clashes
> > between different things that you want to call empty. But Haskell
> > already has a perfectly good language mechanism for doing this --
> > the module system! Why is emptyX preferable to X.empty? The latter
> > convent
Fri, 23 Jun 2000 14:11:04 -0400 (EDT), Chris Okasaki <[EMAIL PROTECTED]> pisze:
> Suppose you have two *classes* that both need/want the same name.
> For example, you may have a class of sequences and a class of finite
> maps that both want to use an empty method. Do you call one emptyS
> and th
On Fri, Jun 23, 2000 at 11:51:56AM +, Steinitz, Dominic J wrote:
> How do I use sockets in Haskell? The ghc manual had some information
> in the users guide (6.7 Interfaces to C libraries) but the sentence
> which started tantalisingly
>
> "Various examples of networking Haskell code are pro
> I have to call Java compiled bytecodes from a Haskell program. So,
> I am looking for some kind of tool or library that implements this kind of
> functionality. The tool should implements this behavior in the same way
> as GHC allows calls to foreign C code.
Hi Herman,
This is what Lamba
I *knew* people couldn't resist talking about names! :-) OK, I've
invited you to do this, but more than a dozen mails solely about the
first item of section 1.1.1 were a little bit surprising...
To be more serious: Perhaps I wasn't clear enough about the purpose of
these conventions. What they're
On Fri, 23 Jun 2000, Chris Okasaki wrote:
(...)
> Also, I've noticed a tendency to shorten the suffixes as much as
> possible (eg, emptyS or emptyFM), in which case you again quickly
> run into name clashes.
(...)
I agree, that is undesirable. Such names get cryptic and are usually
overlooked when
For strange reasons I won't get into here, I would like to implement an
instance of the Functor class for various function types with 1 or more
arguments. I want fmap to transform the result of the function, as
opposed to transforming the first argument.
Once I figured out the syntax, the instan
> > I have to call Java compiled bytecodes from a Haskell program. So,
> > I am looking for some kind of tool or library that implements this kind of
> > functionality. The tool should implements this behavior in the same way
> > as GHC allows calls to foreign C code.
>
> This is what Lambad
21 matches
Mail list logo