-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathdeps.dot
executable file
·54 lines (46 loc) · 1.47 KB
/
deps.dot
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
41
42
43
44
45
46
47
48
49
50
51
52
53
54
//bin/true; exec zsh -c 'meh =(dot -Tsvg deps.dot)'
digraph deps {
create [style=filled fillcolor=red];
compile [style=filled fillcolor=green];
postpone [style=filled fillcolor=cyan];
execute [style=filled fillcolor=yellow];
variable [style=filled fillcolor=magenta];
question [style=filled fillcolor=blue label="???"]
// is it worth using BLUE to mark defining words (words that textually
// consume other words ahead of them)? Or is yellow distinguising enough?
// BLUE executed at edit time? how about BLACK executed at edit time?
// that seems to fit a lot better with the fact that they are usually
// invisible in the editor.
// and what about GRAY?
// and WHITE?
// RULE for colors: a color can only be used to implement a functionality
// that would otherwise not be possible.
find [label="find/mfind"];
editor -> variable;
//rankdir=BT; rankdir=LR;
//variable -> subgraph cluster_foo {a b} -> stack_setup;
stack_setup -> syscalls;
syscalls -> rwx_pages;
rwx_pages -> here;
here -> comma;
syscalls -> key -> word;
syscalls -> persistence;
persistence -> editor;
syscalls -> emit;
here -> compile;
here -> postpone;
write_number -> editor;
word -> find;
word -> create;
word -> read_number;
snorm -> create;
dictionary -> find;
dictionary -> create;
find -> compile;
find -> execute;
find -> postpone;
read_number -> write_number;
emit -> write_number;
stack_setup -> stack_macros;
read_number -> comma;
}