File: Frame.schelp

package info (click to toggle)
supercollider 1%3A3.13.0%2Brepack-1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 80,292 kB
  • sloc: cpp: 476,363; lisp: 84,680; ansic: 77,685; sh: 25,509; python: 7,909; makefile: 3,440; perl: 1,964; javascript: 974; xml: 826; java: 677; yacc: 314; lex: 175; objc: 152; ruby: 136
file content (21 lines) | stat: -rw-r--r-- 570 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
class::Frame
summary:: Stack Frame
categories:: Core>Kernel


description::
Frames are used to contain the arguments, variables and other information for active Functions.

There are no instance variables or methods.

Since Frames are often created on the stack, it is too dangerous to allow access to them. Dangling pointers could result.

Frame instances are inaccessible to the user.

For error handling routines, the relevant information from a Frame can be transferred into a DebugFrame object which can safely be inspected.

code::
	this.getBackTrace.inspect
::