merits of Lisp vs Python

[xscottg at gmail.com]

Paul Rubin wrote:
> xscottg at gmail.com writes:
> > Even regarding interupts, I don't see a problem without a solution:
> >     (with-interupts-and-garbage-collection-disabled
> >        (poke destination (peek source))
>
> It's not just GC or interrupts, it's the possibility of clobbering the
> Lisp heap.  If the peek/poke addresses are restricted to some i/o
> region as Bill suggests, then the above approach may be reasonable.

So don't (poke (random) value).  That would be obvious to anyone
capable of writing a device driver in C or Lisp or Oberon or ....

Cheers,
    -Scott