On Wed, May 12, 2010 at 10:05 PM, Don Stewart wrote:
> martin:
> > hi,
> >
> > since i got no answer from the maintainer, maybe someone else can take
> > care of it, or at least point out, what i did wrong.
> >
> > so, i recently stumbled upon some error while using Text.JSON 0.4.3 [1]:
> >
> >
martin:
> hi,
>
> since i got no answer from the maintainer, maybe someone else can take
> care of it, or at least point out, what i did wrong.
>
> so, i recently stumbled upon some error while using Text.JSON 0.4.3 [1]:
>
> Text/JSON/String.hs:(127,4)-(137,49): Non-exhaustive patterns in case
Hi,
it seems that this was already fixed in the repo, I've put a new
version (0.4.4) on hackage. Thanks, again, for spotting this!
-Iavor
On Wed, May 12, 2010 at 1:24 PM, Daniel Fischer
wrote:
> On Wednesday 12 May 2010 21:53:41, Martin Hilbig wrote:
>> hi,
>>
>> since i got no answer from the m
On Wednesday 12 May 2010 21:53:41, Martin Hilbig wrote:
> hi,
>
> since i got no answer from the maintainer, maybe someone else can take
> care of it, or at least point out, what i did wrong.
>
> so, i recently stumbled upon some error while using Text.JSON 0.4.3 [1]:
>
>Text/JSON/String.hs:(12
Hi,
I think it was probably I who wrote this, so I'll take the blame :-)
It seems like a genuine bug, where we are not checking for strings
that are not terminated. Thanks for spotting it, and also for the
patch! I'll try to update the package soon.
-Iavor
On Wed, May 12, 2010 at 12:53 PM, Marti
hi,
since i got no answer from the maintainer, maybe someone else can take
care of it, or at least point out, what i did wrong.
so, i recently stumbled upon some error while using Text.JSON 0.4.3 [1]:
Text/JSON/String.hs:(127,4)-(137,49): Non-exhaustive patterns in case
indeed ghc warned:
