-
Notifications
You must be signed in to change notification settings - Fork 0
/
notes.txt
105 lines (74 loc) · 2.91 KB
/
notes.txt
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
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
Wed Jun 2 14:06:50 2004
Questions:
- don't you need to wrap set! ?
- why "(parameterize ([current-eval basic-eval]) ... )" ?
- how does you make sure the stepper's annotations were applied?
- how does make-debug-info works?
Open problem in John Clements debugger:
- handle c-w-cm's in the user's code
- handle single stepping, dynamic breakpoints, break button, multiple thread,
current line moves, replay
- name-environment clashes between the user program and the debugger command lines
- do not annotate calls to library functions
- breakpoints in multiple files
Name candidates:
ndg - not a debugger
msg - montreal steak debugger
abc - a bug catcher
The Master
Cybermen
Miranda
Sea Devil
Davros - the creater of the daleks
Ogrons -
Thu Apr 1 17:01:04 2004
Thanks to FrTime, it would be very easy to have multiple
programmers debug that same program remotely.
Wed Mar 31 16:33:05 2004
TODO:
- there is a jdwp event for method exit. I should use it.
- jwatch has to be implemented.
- jstep has to be implemented as well.
- recorders have to be debugged.
Wed Mar 17 17:57:38 2004
People who were working on debugging between 1992 and 2002:
- Christ Fraser at Microsoft
- Somebody at Havard
- Bernd Bruegge and Peter Hibbard on path expressions
You said you were missing papers from the 90s. Here are a
few:
https://research.microsoft.com/~drh/pubs/duel.pdf
https://research.microsoft.com/~drh/pubs/cdb.pdf
https://www.cs.bell-labs.com/sys/doc/acidpaper.ps
https://arxiv.org/pdf/cs.SE/0011010
"
I first recall seeing event pattern languages like this
in a pair of papers that appeared in the 1985 ACM
Symposium on High-Level Debugging. Unfortunately the ACM
electronic archives do not seem to go back that
far. Nonetheless, if the current authors have access to a
copy of the proceedings, they may find relevant papers by
Baiardi and or by Bates and Wileden.
"
Thu Feb 19 19:25:42 2004
Why are behavior defined as list?
Because of letrec and the behavior of merge-e in case of simultaneous events
Why two maps?
(add1 seconds)
(map-e (changes seconds) add1)
Why I am getting "had an undefined stream"?
Try/Catch: what is that right semantics? Dead on uncaught
exception kills all programs during their
construction. Frp should redefine #%module so that programs
are not run during their construction.
Terminaison Criterias: for now it is not possible to control
the target process via a behavior. You could possibly wait
for an event to be generated before restart the target
program. But if your frp program is mainly composed of
behaviors, you cannot tell when a value has converged.
Frp Needs strict/lazy:
Strict suspend dependent computation until the parent
computation has converged. Lazy drops parent computation
until the dependent computation has converged.
How do you do pairs? Should 'nothing' be magic over all behaviors?
How do you do lambda abstraction over frp networks?