Re: XCAR/XCDR as lvalues
Hrvoje Niksic writes:
Kyle Jones <kyle_jones(a)wonderworks.com> writes:
> > Fault handling stuff? That was half a joke. (...)
>
> I like your proposal.
The serious one (XSETCAR/XSETCDR macros), or the fault handling?
The serious one.
The problem with the latter is that it's very non-portable. Yes,
it
would work, but it would require quite a bit of Autoconf work. I've
prepared a patch for trapping stack overflows in a similar fashion,
but I haven't submitted it yet due to its poor portability.
I don't really want to trap SIGSEGV; crashing is fine with
me. The mprotect() thing would be used in conjunction with
your XSETCAR/XSETCDR macros. We not only have to protect
against GC problems in our own code, we have to worry about
code in JKJ-style modules as well. If we can get help from
the hardware/OS, we should take it.