Simon Peyton-Jones wrote:
> | 2. Is there actually anything special about the treatment of stdin, or
> | does this apply to any input stream which is associated with a
> | terminal?
>
> I'm proposing just stdin. My motivation is to make simple stupid
> programs work right.
Argh. Too much of
Simon Peyton-Jones wrote:
> What I intended was
> a simple interactive Haskell program should behave the same
> on any OS/environment
>
> What you and Ross seem to be saying is
> no, the behaviour of the program can, and should, depend
> on the OS/environment
>
> If t
FGL - A Functional Graph Library, Version: September 2002
=
I am happy to announce a new release of the Functional Graph
Library for Haskell, a collection of graph algorithms and tools.
New in this release:
* Introduction of graph clas
On Wednesday, 2002-09-18, 07:22, CEST, Hal Daume III wrote:
> I think this is purely a personal taste kind of thing. First off, though,
> only 'where', 'let', 'of' and 'do' induce layout. I've seen many layout
> styles; the most common seem to be:
>
> let x = ...
> y = ...
> z = .
On Wed, 18 Sep 2002, Simon Peyton-Jones wrote:
> What I intended was
> a simple interactive Haskell program should behave the same
> on any OS/environment
>
> What you and Ross seem to be saying is
> no, the behaviour of the program can, and should, depend
> on the OS/envi
"Simon Peyton-Jones" <[EMAIL PROTECTED]> writes:
> If that's the consensus I'll happily leave echoing
> behaviour unspecified. Remember, that means that a
> conforming implementation can do whatever it pleases, and
> hence it's impossible to write a portable interactive
> Haskell program. Is tha
"Simon Peyton-Jones" <[EMAIL PROTECTED]> writes:
> What I intended was
> a simple interactive Haskell program should behave the same
> on any OS/environment
>
> What you and Ross seem to be saying is
> no, the behaviour of the program can, and should, depend
> on the OS
Ahem how true. I have not idea why it was removed. But I can't put
anything back in at this stage.
Simon
| -Original Message-
| From: Malcolm Wallace [mailto:[EMAIL PROTECTED]]
| Sent: 18 September 2002 10:04
| To: Simon Peyton-Jones
| Cc: [EMAIL PROTECTED]
| Subject: Re: Haskell 98: B
What I intended was
a simple interactive Haskell program should behave the same
on any OS/environment
What you and Ross seem to be saying is
no, the behaviour of the program can, and should, depend
on the OS/environment
If that's the consensus I'll happily leave
Dear Haskellers,
RC 7 of the FFI Addendum is now available from
http://www.cse.unsw.edu.au/~chak/haskell/ffi/
The change log since RC 4, which was the last version
circulated via [EMAIL PROTECTED], is appended below.
Please review this specification carefully. If no
suggestion that leads to
Ross Paterson <[EMAIL PROTECTED]> writes:
> So I favour deletion of the offending sentence, leaving
> this as an environment-dependency.
I second that. I came to Haskell after many other
programming languages, and was VERY surprised by echo
behaviour. I vote for consistency with long-standing
> From: D. Tweed [mailto:[EMAIL PROTECTED]]
>
> Note that (assuming that I'm not missing something) you can
> prevent the
> moving of expressions involving l in a very ugly way by
> noting that these
> `dummy argument functions' are polymorphic so that you could write
>
> x1 = f1 (l 1)
> x2 =
On 17 Sep 2002, Jan Kybic wrote:
> > > > collection. I want to try to force l to be generated on-the-fly
> > > > every time it is needed, to see if it improves performance.
> > > > What is a good way to do it? Would something like
> > > >
> > ...
> > > The easiest way is to make it a function
> >
On Wed, Sep 18, 2002 at 09:21:02AM +0100, Simon Peyton-Jones wrote:
> | No yelling, but some random points for consideration:
> |
> | 1. It might be worth being more explicit, i.e. stating whether this is
> | because the runtime explicitly enables echoing, or because it's
> | assumed that echoing
"Simon Peyton-Jones" <[EMAIL PROTECTED]> writes:
> (You can change echoing settings via the IO.hSetEcho etc.)
Ahem, one of the deficiencies of Haskell'98 is that there is no function
IO.hSetEcho. There used to be one in Haskell 1.3 I think, so I guess there
was a good reason for removing it?
R
| No yelling, but some random points for consideration:
|
| 1. It might be worth being more explicit, i.e. stating whether this is
| because the runtime explicitly enables echoing, or because it's
| assumed that echoing will already be enabled.
Well, at Haskell user doesn't care. It's precisely
16 matches
Mail list logo
