On Sun, Mar 15, 2009 at 9:13 PM, Bryan O'Sullivan wrote:
> On Sun, Mar 15, 2009 at 8:40 PM, Alexander Dunlap
> wrote:
>>
>> I have noticed that in both Data.Binary and Data.Text (which is still
>> experimental, but still), the "decode" functions can be undefined
>> (i.e. bottom) if they encounter
On Monday 16 March 2009 06:40:12 Alexander Dunlap wrote:
> Hi all,
>
> I have noticed that in both Data.Binary and Data.Text (which is still
> experimental, but still), the "decode" functions can be undefined
> (i.e. bottom) if they encounter malformed input.
>
> What is the preferred way to use th
On Sun, Mar 15, 2009 at 8:40 PM, Alexander Dunlap <
alexander.dun...@gmail.com> wrote:
>
> I have noticed that in both Data.Binary and Data.Text (which is still
> experimental, but still), the "decode" functions can be undefined
> (i.e. bottom) if they encounter malformed input.
>
For decoding Un
Hi all,
I have noticed that in both Data.Binary and Data.Text (which is still
experimental, but still), the "decode" functions can be undefined
(i.e. bottom) if they encounter malformed input.
What is the preferred way to use these functions in a safe way? For
example, if one writes data to a dis
