File: hints.bs

package info (click to toggle)
storm-lang 0.7.5-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 52,028 kB
  • sloc: ansic: 261,471; cpp: 140,432; sh: 14,891; perl: 9,846; python: 2,525; lisp: 2,504; asm: 860; makefile: 678; pascal: 70; java: 52; xml: 37; awk: 12
file content (40 lines) | stat: -rw-r--r-- 1,497 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
/**
 * Visualization hints for a language.
 *
 * A language may modify the behavior of the visualization by providing an implementation of the
 * function 'hints' in the same package as the 'reader' function used for the language. If no
 * special implementation is provided, the system uses DefaultHints instead.
 *
 * This object is in charge of two parts, represented as two different objects that are members of
 * different threads.
 *
 * First and foremost, the Hints class is responsible for injecting code in the generated code from
 * the language. These calls will notify the Program class of the status of the current execution,
 * and the values of local variables.
 *
 * Secondly, the ViewHints class is responsible for interpreting the collected data. It has a chance
 * to intercept what is shown for objects on the stack, and gets the opportunity to provide custom
 * visualizations for types that are built into the language itself. When multiple languages are
 * used simultaneously, the ViewHints gets exclusive access to the appearance of objects on the
 * stack and joint responsibility for objects on the heap.
 */
value Hints {
	// Code hints.
	CodeHints code;

	// View hints.
	progvis:data:ViewHints? view;

	init(CodeHints code) {
		init() { code = code; }
	}

	init(CodeHints code, progvis:data:ViewHints view) {
		init() { code = code; view = view; }
	}
}

// Create standard hints.
Hints defaultHints() {
	Hints(DefaultCodeHints(), progvis:data:DefaultViewHints());
}