simonmar:
> Donald Bruce Stewart wrote:
> >Binary: high performance, pure binary serialisation for Haskell
> > --
> >The Binary Strike Team is pleased to announce the release of a new,
> >pure, efficient binary seriali
Donald Bruce Stewart wrote:
Binary: high performance, pure binary serialisation for Haskell
--
The Binary Strike Team is pleased to announce the release of a new,
pure, efficient binary serialisation library for H
Hi
> I also fear that the existing script does not handle types with more than
> 256 constructors correctly. While uncommon, those are not unrealistic.
Feel free to send in a patch. All it needs to do is check if there are
more than 2^8 constructors and if so encode the tag in a Word16 rather
t
On Fri, 2007-01-26 at 15:40 +0100, Arie Peterson wrote:
> Hello,
>
>
> Donald Bruce Stewart wrote:
>
> > Ok, I forgot one point. It is possible to automatically derive instances
> > of Binary for your custom types, if they inhabit Data and Typeable,
> > using an SYB trick. Load tools/derive/Bina
On Fri, Jan 26, 2007 at 03:40:42PM +0100, Arie Peterson wrote:
> Using DrIFT would probably automate the deriving just as well, but in my
> particular situation TH support is easier to maintain than DrIFT support.
DrIFT as of 2.2.1 now supports binary for this package. using it is as
simple as thi
On Fri, Jan 26, 2007 at 03:12:29PM +, Dougal Stanton wrote:
> Quoth Arie Peterson, nevermore,
> > I also fear that the existing script does not handle types with more than
> > 256 constructors correctly. While uncommon, those are not unrealistic.
>
> "256 constructors ought to be enough for an
Joel Reymont wrote:
> May I ask why TH is easier to maintain than DrIFT?
>
> I'm not familiar with DrIFT.
The reason is personal, and very silly. I only use ghc, so TH is available
automatically.
Like you, I have never used DrIFT, so I would have to get to know it, and
install it everywhere I wa
Quoth Arie Peterson, nevermore,
> I also fear that the existing script does not handle types with more than
> 256 constructors correctly. While uncommon, those are not unrealistic.
"256 constructors ought to be enough for anybody"? ;-)
Seriously though, the thought of a type definition that heavy
On Jan 26, 2007, at 2:40 PM, Arie Peterson wrote:
Using DrIFT would probably automate the deriving just as well, but
in my
particular situation TH support is easier to maintain than DrIFT
support.
May I ask why TH is easier to maintain than DrIFT?
I'm not familiar with DrIFT.
Why would I
Hello,
Donald Bruce Stewart wrote:
> Ok, I forgot one point. It is possible to automatically derive instances
> of Binary for your custom types, if they inhabit Data and Typeable,
> using an SYB trick. Load tools/derive/BinaryDerive.hs into ghci, and
> bring your type into scope, then run:
>
>
10 matches
Mail list logo
