IOError vs. Exception vs. IOException

Simon Marlow
Mon, 4 Nov 2002 15:15:10 -0000

> On Mon, Nov 04, 2002 at 01:00:39PM -0000, Simon Marlow wrote:
> > Our feeling over here is that this is an unforced change, so in
> > isolation it probably wouldn't be worthwhile.  It'll break=20
> some code,
> > and the awkward squad paper will have to be updated to=20
> comply (although
> > we just noticed it is already wrong about the behaviour of
> > Prelude.catch).
> What should other implementations do?

I'm not sure I understand the question - other implementations should
follow whatever is decided for the library interface, right?=20

I'm really not arguing either way, in fact I like the change, but
perhaps we should think hard before breaking code.  I haven't heard
anyone else comment so far on whether they like/dislike the current
Exception interface... anyone?