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
..
command.scm	Remove `procedure' repl command	2015-12-01 11:30:54 +01:00
common.scm	Merge branch 'stable-2.0'	2014-01-14 01:30:56 -05:00
coop-server.scm	Add cooperative REPL server module.	2014-02-12 11:26:22 -05:00
debug.scm	Frame <binding> objects capture frame, can ref value directly	2016-01-31 11:15:58 +01:00
describe.scm	Use 'substring' instead of obsoleted 'make-shared-substring'	2011-02-02 05:45:37 -08:00
error-handling.scm	Out-of-memory situations raise exceptions instead of aborting	2014-03-22 15:49:31 +01:00
repl.scm	Add cooperative REPL server module.	2014-02-12 11:26:22 -05:00
server.scm	Add cooperative REPL server module.	2014-02-12 11:26:22 -05:00