From: Robert Dober <robert.dober@...>
Date: 2007-05-18T17:55:50+09:00
Subject: Re: "Crystallizing" Objects

On 5/18/07, Robert Klemme <shortcutter@googlemail.com> wrote:
<snip>
> > Has a similar idea been discussed before?
>
> I am not aware of something like this.  But it's good to discuss
> suggestions like this from time to time. :-)

I feel that the idea is worth discussing out of the synchronization
issue. I do not think it is fit for that purpose.
However the idea of an object state that allows to add information but
forbids the loss/overwriting of information is just great.

Maybe an example is better

class History < Array # for shortness of code, I'd probably use deleagtion
    def initialize
        no_loss # --> that is the semi frozen state
    end
end
h= History.new
h << "Just lost my SVN Server"
h << "My dog eat my flash disk, the small one (dog not disk)"
puts h ==>  "2007-05-16 14:13:12 Just lost my SVN Server\n...."
h.pop ==> TypeError: cannot remove/modify information in a no_loss object <....>

I just feel that would be nice to have.

Cheers
Robert

>
> Kind regards
>
>         robert
>
>


-- 
You see things; and you say Why?
But I dream things that never were; and I say Why not?
-- George Bernard Shaw