iteratee darcs patch: bump version range dependency for 'failure'

[John Lato]

NothingException should never be thrown.  I wanted to define
"enumFromCallback" using enumFromCallbackCatch and needed to supply a
default handler.  In particular, the default handler needs to instantiate a
concrete exception type and also not actually catch any real exceptions.
Using "NothingException" seemed the cleanest route; the only other real
option is to catch SomeException and re-throw it.

Iteratee could define NothingException internally, but I like the failure
package so I just used it from there to avoid name conflicts.

John

On Mon, Aug 16, 2010 at 11:25 PM, Antoine Latter <aslatter at gmail.com> wrote:

> Yeah, I was trying to rip out the dependency entirely but it wasn't
> immediately clear to me how the NothingException was being thrown.
>
> I'm all for minimizing depedencies, but 'failure' is about as harmless as
> it gets.
>
> Antoine
>
> On Aug 16, 2010 5:01 PM, "John Lato" <jwlato at gmail.com> wrote:
>
>
>
> On Mon, Aug 16, 2010 at 4:57 AM, Antoine Latter <aslatter at gmail.com>
> wrote:
> >
> > On Sun, Aug 15, 2010...
>
> It's highly unlikely that a version bump in failure will cause problems.
> I'm only using 'failure' for the "NullException" and "NothingException"
> classes, neither of which have any methods.  NothingException is then used
> for the default exception handler in "enumFromCallback".  I wouldn't need to
> depend on failure at all, except I rather like the library.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://projects.haskell.org/pipermail/iteratee/attachments/20100816/02ce1902/attachment.htm