Alastair Reid <[EMAIL PROTECTED]> writes:

> But some of us have to write programs that keep working.  For example, 
> I'm busy hacking on our Robo-Haskell code at the moment - it just isn't
> acceptable for that kind of code to print an error message and halt.
> I remain convinced that:
> 
>   Haskell will remain a toy language until it can be used to write
>   robust programs.

I agree.

> As far as I can see, that means we either have to eliminate pattern
>  match failure, the error function, heap overflow, stack overflow
>  and infinite loops or we have to add exception handling in some form.

And I agree with this list, except for infinite loops.  How will
exceptions help make a program robust that otherwise might loop?

Carl Witty
[EMAIL PROTECTED]


Reply via email to