|
On Thu, 20 May 2004 11:00:08 -0400 Hans Boldt <boldt@xxxxxxxxxx> wrote: > It's because you're dealing with stack storage. At any > time after the procedure returns, that area of storage is > subject to reuse, typically by calls to other procedures, > but also (depending on CPU and O/S) by random machine > interrupts. Simply, you just can't trust anything on the > popped side of the stack pointer on any hardware. (For > me, it's a lesson I learned the hard way while writing a > LISP interpreter in PDP-11 assembler language way back in > 1978.) Ok, that's what I assumed. Thanks for the info!
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.