Re: Properties and readonly objects

Tuesday, 13 April 1999

        sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes:

...
 >>>>> "Hrvoje" == Hrvoje Niksic
<hniksic(a)srce.hr&gt; writes:

 Hrvoje> BTW, why do we want Lisp-level readonly objects in the first
 Hrvoje> place?

 The most obvious is that, with the right dumper and OS support, you
 can put them in shareable/read-only/EPROM memory. 
Isn't this the point of C-level readonly objects?  If I understand
Olivier correctly, the "lisp-level readonly objects" would still be
modifiable from C, which would make them unsuitable for
shareable/read-only memory.

Or am I misunderstanding Olivier?

...
 Another is that you can optimize GC with this kind of knowledge.  It
 seems that, since reachability is affected by mutable plists, you
 want the plists of immutable objects to be immutable as well. 
Hmm.  The old "pure" stuff behaved this way for strings.  It took the
easy way out for symbols, simply refusing to create pure symbols.

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998