5 Aug
2009
5 Aug
'09
5:14 p.m.
On Wed, Aug 05, 2009 at 01:47:07PM -0700, Donald Bruce Stewart wrote:
alexander.dunlap:
OK. Would it be worth creating an extensible exception (something like BinaryDecodeError) for this then, instead of using the call to error? That would at least make it less error-prone to catch.
I think that would be a good idea. Showing how to catch it in the documentation.
I'm wary of breaking the 70 packages that use Data.Binary for this, rather, add this as a list of API changes for the next major release.
If you're planning a change that you are worried would break users of the package, wouldn't it be better to do it before putting it into the platform? Or have I misunderstood what you meant? Thanks Ian