Re: XCAR/XCDR as lvalues
Jan Vroonhof <vroonhof(a)math.ethz.ch> writes:
Hrvoje Niksic <hniksic(a)srce.hr> writes:
> I don't know if we do.
We do (at least it seems so from lisp.h).
Then how come I can't get a crash out of X[AC]DR being an lvalue?
Kyle reported that this got hosed when we started using ELF-style
binaries. Can someone who understands these things elaborate?
(Please avoid the "copy-on-write" syntagm in the elaboration -- I'm
alergic. :-)
> > They do COW don't they?
>
> Isn't it a better policy to keep the shared segments read-only?
Unexec'ing puts the pure stuff the .data segment if I am not
mistaken:
[...]
Quite possible, but this might also be considered a bug.
So the question is now: Is XEmacs used at all on platforms which do
require a true read-only purespace.
Kyle reported that BSD/OS uses a read-only purespace. Anyway, I think
you are misusing the word "require". In my opinion, read-only
purespace is a *feature*. We want the purespace to be shared. In
this case, we *don't* want the mythical COW.