Forgot to post the link to the code, you can do a darcs pull from my
repo:
darcs -p 'added.*freezing.*' http://repos.blurgle.ca/darcs/io
On 18-Jun-06, at 3:31 PM, Jeremy Tregunna wrote:
> Last night, I whipped up a quick patch to provide object freezing for
> a lot of the objects in the VM (potentially not all, which is why I'm
> posting this).
>
> What this does is prevent any further modifications to an object for
> as long as the object is alive (no way to thaw objects yet, and I'm
> holding off until we have a security policy in place that would cover
>; these sorts of things). Note: You will still be able to replace the
> object on a particular slot, but the object will still be frozen.
>
> Anyhow, I haven't patched any bindings yet (just the collections or
> any that modify internal state), only the VM's collections and
> setSlot/updateSlot.
>
> Comments, criticisms as always, are welcome.
>
> --
> Jeremy Tregunna
> jtregunna
blurgle.ca
>
>
> "One serious obstacle to the adoption of good programming languages
> is the notion that everything has to be sacrificed for speed. In
> computer languages as in life, speed kills." -- Mike Vanier
>
>
>
> ------------------------ Yahoo! Groups Sponsor --------------------
> ~-->
> See what's inside the new Yahoo! Groups email.
> http://us.click.yahoo.com/2pRQfA/bOaOAA/yQLSAA/saFolB/TM
> ----------------------------------------------------------
> ~->
>
>
> Yahoo! Groups Links
>;
>
>
>
>
>
>
> !DSPAM:4495a97c11972011796794!
>
--
Jeremy Tregunna
jtregunnablurgle.ca
";One serious obstacle to the adoption of good programming languages
is the notion that everything has to be sacrificed for speed. In
computer languages as in life, speed kills." -- Mike Vanier