merits of Lisp vs Python

[Paul Rubin]

Bill Atkins <not-a-real-email-address at not-a-real-domain.com> writes:
> Whatever do you mean?  The portion of memory used for memory-mapped
> registers is simply excluded from GC; everything else works as normal.

Well ok, if the peek and poke functions validate the addresses.

> All modern Lisps (yes, *Common* Lisps) support a foreign-function
> interface to talk to C libraries.  Data involved with these kinds of
> interface is ignored by the GC, for obvious reasons.  Do you claim
> that these implementations are not truly Lisps?

I think usually those objects are simply treated as opaque by the GC
and the contents are inaccessible except through FFI calls.  You can't
have the Lisp code running amuck trampling things through naked
pointers.  Obviously the foreign function can trample things but it's
not written in Lisp.