Hi all, We've had Control.OldException, and the new Control.Exception, since GHC 6.10.1, and since 6.12.1 using Control.OldException has given the deprecation message Future versions of base will not support the old exceptions style. Please switch to extensible exceptions. I propose that we now remove it from base. If some people still cannot use the new Control.Exception for some reason, then it could be maintained in an old-exception package. Discussion deadline: 18 Feb 2012. Thanks Ian
+1 Just out of curiosity, are there any major packages (e.g. in the HP) that still use old exceptions? -- Johan
On Fri, 3 Feb 2012, Ian Lynagh wrote:
We've had Control.OldException, and the new Control.Exception, since GHC 6.10.1, and since 6.12.1 using Control.OldException has given the deprecation message Future versions of base will not support the old exceptions style. Please switch to extensible exceptions.
I propose that we now remove it from base.
If some people still cannot use the new Control.Exception for some reason, then it could be maintained in an old-exception package.
I prefer to have an old-exception package. I guess it is the only way to cope with IO exceptions in a Haskell 98 way.
On 03/02/2012 21:00, Henning Thielemann wrote:
On Fri, 3 Feb 2012, Ian Lynagh wrote:
We've had Control.OldException, and the new Control.Exception, since GHC 6.10.1, and since 6.12.1 using Control.OldException has given the deprecation message Future versions of base will not support the old exceptions style. Please switch to extensible exceptions.
I propose that we now remove it from base.
If some people still cannot use the new Control.Exception for some reason, then it could be maintained in an old-exception package.
I prefer to have an old-exception package. I guess it is the only way to cope with IO exceptions in a Haskell 98 way.
Could you clarify what you want to do? System.IO.Error would still be supported, which provides ioError and catch. Cheers, Simon
On Tue, 7 Feb 2012, Simon Marlow wrote:
On 03/02/2012 21:00, Henning Thielemann wrote:
I prefer to have an old-exception package. I guess it is the only way to cope with IO exceptions in a Haskell 98 way.
Could you clarify what you want to do? System.IO.Error would still be supported, which provides ioError and catch.
So far I was used to import Control.Exception for bracket and ioError and catch. If this continues to work with System.IO.Error, I am happy.
On 07/02/2012 12:48, Henning Thielemann wrote:
On Tue, 7 Feb 2012, Simon Marlow wrote:
On 03/02/2012 21:00, Henning Thielemann wrote:
I prefer to have an old-exception package. I guess it is the only way to cope with IO exceptions in a Haskell 98 way.
Could you clarify what you want to do? System.IO.Error would still be supported, which provides ioError and catch.
So far I was used to import Control.Exception for bracket and ioError and catch. If this continues to work with System.IO.Error, I am happy.
Well, if you are using Control.Exception then you won't be affected - the proposal is to remove Control.OldException. Cheers, Simon
participants (8)
-
Bas van Dijk -
Felipe Almeida Lessa -
Henning Thielemann -
Ian Lynagh -
Ivan Lazar Miljenovic -
Johan Tibell -
shelarcy -
Simon Marlow