> > As such, it seems tough to
> > write libraries right now as the upcoming GHC/Hugs release will contain
> > features that strongly affect library design:
> >
> > * multi-parameter type classes
>
> etc... all seem to be things that are waiting 'till Haskell 2. My
> point was that _something_ should be in Standard Haskell.
I agree that we don't have to wait for MPTC, exceptions and the like.
MPTC can make things cleaner but the existing Hugs-GHC libraries are
managing ok without them. Likewise, adding exception handling
might affect how things are done if fetching URLs is outside the
IO monad - but it won't affect it that much and it's not clear that
fetching URLs outside the IO monad is sensible. Not at all clear.
That said, I think it's premature to talk of putting this in a standard
library when we don't even have an implementation never mind experience
with whether we have the right design or not. I propose the following
approach:
1) Implement something (anything) and play with it.
2) Port it to lots of implementations and platforms fixing any
obvious deficiencies in the interface as we go.
3) Let the dust settle.
4) Add it to the Hugs-GHC library collection (which makes sure it's
documented and distributed with Hugs and GHC).
5) Let the dust settle.
6) Consider whether it's ready for standardisation.
Any volunteers for steps 1 and 2?
--
Alastair Reid Yale Haskell Project Hacker
[EMAIL PROTECTED] http://WWW.CS.Yale.EDU/homes/reid-alastair/
