On 31 December 2011 17:44, Timothy Baldridge wrote:
> Yeah, I hadn't thought of the issue of the refs, but I don't think
> it's a exceptionally hard problem to solve.
It's not really possible to solve completely.
If I serialize, then deserialize an immutable data structure, then for
all intents
First of all, I've updated the README.md to show the license. It's a
BSD 3 clause license.
Yeah, I hadn't thought of the issue of the refs, but I don't think
it's a exceptionally hard problem to solve. What we are discussing is
basically the same thing that mutable languages deal with every day.
A
On 31 December 2011 08:08, Meikel Brandmeyer wrote:
> I think, what James wants to say is: serialising reference types is
> non-trivial. Reference types are identities. So the instance itself (as in
> identical?) carries information. When you have references to a ref you have
> to make sure tha
> I think, what James wants to say is: serialising reference types is
> non-trivial. Reference types are identities. So the instance itself (as in
> identical?) carries information. When you have references to a ref you have
> to make sure that they all refer to the same ref again after thawing.
Hi,
Am 31.12.2011 um 05:36 schrieb Peter Taoussanis:
>> I guess what I'd like a mode where I can say "act like read/pr" and> for
>> deep-freeze to ignore metadata, refs and atoms.
>
> I'm still not sure I'm getting this argument though. In its current
> form, deep-freeze makes an attempt to pre
On 30 December 2011 17:00, Timothy Baldridge wrote:
> A few months back I released 1.0 of deep-freeze, a binary
> serialization library for Clojure. Due to recent additions by Peter
> Taoussanis I thought it would be about time to let some more people
> know about this project, and bump the versi
> I guess what I'd like a mode where I can say "act like read/pr" and> for
> deep-freeze to ignore metadata, refs and atoms.
I'm still not sure I'm getting this argument though. In its current
form, deep-freeze makes an attempt to preserve as much information as
it can. In the specific case of ST
On 30 December 2011 18:54, Timothy Baldridge wrote:
>> I think it might be more useful if freeze/thaw worked on the same
>> domain as read/pr by default. That way I can swap in and out different
>> serialization functions without altering the behaviour of the
>> application.
>
> Well, from my view
> I think it might be more useful if freeze/thaw worked on the same
> domain as read/pr by default. That way I can swap in and out different
> serialization functions without altering the behaviour of the
> application.
Well, from my view, read-string/print-str is completely broken when it
comes t
On 30 December 2011 17:42, Peter Taoussanis wrote:
>> It would be nice if there was an option to make deep-freeze
>> interchangable with read/pr.
>
> Hmm- I don't follow. Interchangeable how? Could you explain what use
> you have in mind?
Well, currently it's not directly interchangeable because
> How are atoms/refs supported?
Very simply: they're just dereferenced during freezing and that value
is reinserted into an atom/ref/whatever during thawing. Any metadata
is also retained.
> It would be nice if there was an option to make deep-freeze
> interchangable with read/pr.
Hmm- I don't f
On Fri, Dec 30, 2011 at 8:38 AM, James Reeves wrote:
> On 30 December 2011 06:00, Timothy Baldridge wrote:
>> A few months back I released 1.0 of deep-freeze, a binary
>> serialization library for Clojure.
>
> You might want to provide a link to the project home page :)
>
Wow, I can't believe I
On 30 December 2011 06:00, Timothy Baldridge wrote:
> A few months back I released 1.0 of deep-freeze, a binary
> serialization library for Clojure.
You might want to provide a link to the project home page :)
> deep-freeze is a simple serialization library that aims to be fast,
> generate conci
13 matches
Mail list logo
