On Mon, 07 Aug 2000 22:50:59 -0400, Buddha Buck wrote: >They represent the -entire- future history of the program. The "future history" doesn't exist just yet. All you can do is save the entire current state of the program, so you can redo everything from this point on, later, over and over again. This sounds a bit like the functionality offered by "dump"; except that that one does not save the call stack. -- Bart.
- Re: RFC 47 (v1) Universal Asynchronous I/O John Tobey
- Re: RFC 47 (v1) Universal Asynchronous I/O Bart Lateur
- Re: RFC 47 (v1) Universal Asynchronous I/O Piers Cawley
- Re: RFC 47 (v1) Universal Asynchronous I/O John Tobey
- Re: RFC 47 (v1) Universal Asynchronous I/O Piers Cawley
- Re: RFC 47 (v1) Universal Asynchronous I/O John Tobey
- Re: RFC 47 (v1) Universal Asynchronous I/O Bart Lateur
- Re: RFC 47 (v1) Universal Asynchronous I/O Buddha Buck
- Re: RFC 47 (v1) Universal Asynchronous I/O John Tobey
- Re: RFC 47 (v1) Universal Asynchronous I/O Ken Fox
- Bart Lateur