Andy Wingo cd0b61a04e Frame <binding> objects capture frame, can ref value directly ... * module/system/repl/debug.scm (print-locals): Adapt to frame-binding-ref change. * module/system/vm/frame.scm (<binding>): Add `frame' field. (available-bindings): Capture the frame. (binding-ref, binding-set!): New functions, accessing a local variable value directly from a frame. (frame-binding-ref, frame-binding-set!): Remove. As these are very low-level debugging interfaces introduced in 2.0, never documented, and quite tied to the VM, we feel comfortable making this change. (frame-call-representation): Adapt to available-bindings change. (frame-environment, frame-object-binding): Adapt to binding-ref interface change. * doc/ref/vm.texi (Stack Layout): Mention that slots can be re-used. Update disassembly in example. * doc/ref/api-debug.texi (Frames): Remove documentation for frame-local-ref, frame-local-set!, and frame-num-locals. Replace with documentation for frame-bindings, binding accessors, and binding-ref / binding-set!.		2016-01-31 11:15:58 +01:00
..
base	(system base types) knows about variables	2015-02-17 10:58:29 +01:00
repl	Frame <binding> objects capture frame, can ref value directly	2016-01-31 11:15:58 +01:00
vm	Frame <binding> objects capture frame, can ref value directly	2016-01-31 11:15:58 +01:00
foreign-object.scm	Add #:static-slot-allocation?	2015-02-06 13:25:17 +01:00
foreign.scm	Merge commit 'f6ddf827f8'	2014-02-07 14:51:42 +01:00
xref.scm	rtl-program? -> program?	2013-11-19 19:11:40 +01:00