From: John Peterson [EMAIL PROTECTED]
To: haskell@haskell.org
Subject: Blown disk on haskell.org
Sorry for the downtime - haskell.org lost a disk today. Everything is
back to normal (I hope). If you have software installed there, we
upgraded to a new OS. Hope this doesn't break anything!
From: John Peterson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [Haskell-cafe] Functional Reactive Programming
Functional Reactive Programming is alive but in need of some new
students to push the effort a bit. A lot of us have taken teaching
or industrial positions so the old FRP team
We're aware of the wiki problems. We've got out wiki guy working on
it and I hope everything will be working again soon. We won't lose
anything that's been posted to the wiki. Please be patient!
John
___
Haskell-Cafe mailing list
[EMAIL
Hi all. Too many people on vacation is the real problem with the
wiki. Should be back in operation soon.
John
___
Haskell-Cafe mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/haskell-cafe
I hope everyone has enjoyed spam-free lists for the last couple of
weeks. I've been moderating the spam away but I'm changing over to an
automated spam tool, spam assassin. This is what the local support
folks are starting to use throughout the campus and I'm going to defer
to them in the spam
You might look at the geometry library in Fran (you can find a link in
haskell.org to Fran if you need it). It implements points and vectors
similar to what you're looking for. To answer your questions, you
can't (in standard Haskell) use the conventional operator names for
all of the
WASHINGTON - A little known computer language offers hope for Y2K
computer problems. With the federal government falling behind in the task
of preparing its computers for the year 2000, experts are turning to a
small startup company, Lambdametrics, to address the Y2K bug, a
problem that arises
ANNOUNCEMENT AND CALL FOR PAPERS
The Third Haskell Workshop
http://www.haskell.org/HaskellWorkshop.html
Friday October 1st, 1999, Paris, France
The Third Haskell Workshop will take place in Paris, France as part of
PLI'99. Co-located conferences include ICFP, PPDP (previously
You can't nuke monomorphism without addressing the ambiguity problem.
At the very least, you need scoped type variables to disambiguate
types in the absence of the MR. This ambiguity is a definite pitfall
and the type errors resulting from this ambiguity will probably be
even more puzzling and
Attention graphic designers! We need a logo for Hugs! See
haskell.org/hugs/logo.html for details about the Hugs logo contest.
Win prizes!!
John
I can't speak for Hugs 1.3c, but Hugs 1.4 and prior systems use the
proposed monomorphism rule, not the Haskell 1.4 rule.
John
I don't understand the opposition to changing the default default to
Integer. This certainly won't break anything in any sort of serious
way (only for exported values with no type signature attached),
probably has only a minimal effect on performance - quite easily
corrected using type
We just found out last week that messages sent to
[EMAIL PROTECTED] were not being correctly forwarded and
sitting unattended in a mailbox at Yale for over a year (!). We hope
that all of the problems with the mailing list are now resolved. We
have processed the backlog of messages and I'm sure
We would like to invite everyone to check out the "all new"
haskell.org. I've added a section on using Haskell in classes (thanks
again to all who responded!) and Olaf Chitil has integrated
haskell.org with his Haskell site to produce a much nicer web site.
Olaf did all the hard work on this - I
I hate to reopen an old debate but here goes.
While some may argue that avoiding re-evaluation is the justification
for the monomorphism restriction, the real issue is ambiguity.
Without some form of monomorphism (or scoped type variables?? Someone
needs to convince me that scoped type
Microsoft And Yale Conclude Agreement To License Technology For Haskell
Microsoft Demonstrates Haskell-Compatible Browser and Tools
NEW HAVEN - April 1, 1998 - At a press conference today Microsoft Corp.
(Nasdaq: MSFT) announced it has concluded an agreement to license the
Haskell programming
I had option 1 in mind when that part of the report was written. We
should clarify this in the next revision.
And thanks for your analysis of the problem!
John
All special syntax, like (), resolves to Prelude names regardless of
imports. Your second try is correct - it's hbc that's broken.
John
This is certainly a small bug in the Hugs Prelude. If you look at the
1.4 report, the order of the constructors is correct. I think this
bug went back to the 1.2 report and has been sitting in the Hugs
prelude since then. This will be fixed in the official Hugs 1.4
release.
John
This is definitely a bug in the syntax of Haskell. I don't see any
simple fix to the grammar except to change var to qvar in pat and
apat. This probably isn't a good idea since it would allow local
variables whihc shadow qualified imports or some such. We could add a
line saying `qualifiers
Changes to the Haskell 1.3 Prelude
The following changes have been proposed (or accepted) for Haskell 1.3.
* Reorganize the Ord class
* Add succ and diff to Enum
* Add new class "Bounded"
* Add strictness annotation to Complex and Ratio
*
Introducing Haskell 1.3
This new version of the Haskell Report adds many new features to the
Haskell language. In the five years since Haskell has been available
to the functional programming community, Haskell programmers have
requested a number of new language features. Most of these
22 matches
Mail list logo