
http://haskell.org/haskellwiki/Upgrading_packages#Typical_breakages_with_GHC... It collects the 7 or so known issues that break code with GHC 6.10. Please feel free to clean up, and especially *add techniques for handling each change*. If we do this right, with cabal-install being smart, clear summaries of what is broken and how to fix it, this might be the smoothest major release yet. -- Don

Hello Don, Saturday, October 11, 2008, 9:21:47 PM, you wrote:
It collects the 7 or so known issues that break code with GHC 6.10.
i've quickly tried to compile my app with 6.10 (using base4). all the problems i got was due to exception handling. catch, finally, throwIO doesn't work added to wiki -- Best regards, Bulat mailto:Bulat.Ziganshin@gmail.com

bulat.ziganshin:
Hello Don,
Saturday, October 11, 2008, 9:21:47 PM, you wrote:
It collects the 7 or so known issues that break code with GHC 6.10.
i've quickly tried to compile my app with 6.10 (using base4). all the problems i got was due to exception handling. catch, finally, throwIO doesn't work
added to wiki
The fix for exception handling and friends is to add a dependency on base-3, http://haskell.org/haskellwiki/Upgrading_packages#Adding_base-3_constraints If you build your app with cabal-install, it will work this out for you, otherwise, you need to add something like --constraint="base<4" if you use runhaskell, or --package base-3.0.3.0 if you use ghc --make. -- Don

Hello Don, Saturday, October 11, 2008, 9:54:10 PM, you wrote: seems that i misunderstood it: i thought it's a list of base4 vs base3 changes, but actually it seems like a base30 vs base31? base3 -> base4 upgrade hints are not documented anywhere?
bulat.ziganshin:
Hello Don,
Saturday, October 11, 2008, 9:21:47 PM, you wrote:
It collects the 7 or so known issues that break code with GHC 6.10.
i've quickly tried to compile my app with 6.10 (using base4). all the problems i got was due to exception handling. catch, finally, throwIO doesn't work
added to wiki
The fix for exception handling and friends is to add a dependency on base-3,
http://haskell.org/haskellwiki/Upgrading_packages#Adding_base-3_constraints
If you build your app with cabal-install, it will work this out for you, otherwise, you need to add something like
--constraint="base<4"
if you use runhaskell, or
--package base-3.0.3.0
if you use ghc --make.
-- Don
-- Best regards, Bulat mailto:Bulat.Ziganshin@gmail.com

bulat.ziganshin:
Hello Don,
Saturday, October 11, 2008, 9:54:10 PM, you wrote:
seems that i misunderstood it: i thought it's a list of base4 vs base3 changes, but actually it seems like a base30 vs base31?
base3 -> base4 upgrade hints are not documented anywhere?
It's a list of how to upgrade your code to GHC 6.10 and keep it working. If you want to describe how to migrate from base3 to base4, that is also useful, but not criical yet, since it won't break things. -- Don

Don Stewart wrote:
http://haskell.org/haskellwiki/Upgrading_packages#Typical_breakages_with_GHC...
It collects the 7 or so known issues that break code with GHC 6.10. Please feel free to clean up, and especially *add techniques for handling each change*.
If we do this right, with cabal-install being smart, clear summaries of what is broken and how to fix it, this might be the smoothest major release yet.
This is wonderful. I've been making noises about trying to make the transition smoother this time, but you and Duncan have done most of the hard work. Not only that, but the process has turned up some bugs that hopefully we'll be able to fix in time for the release. Great stuff, thanks guys! Cheers, Simon

| http://haskell.org/haskellwiki/Upgrading_packages#Typical_breakages_with_GHC... | 6.10 | > | > It collects the 7 or so known issues that break code with GHC 6.10. | > Please feel free to clean up, and especially *add techniques for | > handling each change*. | > | > If we do this right, with cabal-install being smart, clear summaries of | > what is broken and how to fix it, this might be the smoothest major | > release yet. | | This is wonderful. I've been making noises about trying to make the | transition smoother this time, but you and Duncan have done most of the | hard work. Not only that, but the process has turned up some bugs that | hopefully we'll be able to fix in time for the release. Great stuff, | thanks guys! Yes, a big thank you from me too. Fantastic work. Simon
participants (4)
-
Bulat Ziganshin
-
Don Stewart
-
Simon Marlow
-
Simon Peyton-Jones