freenode/#lisp - IRC Chatlog
Search
3:28:47
drmeister
Is there some special return value that the handler returns to indicate that it does or doesn't handle the condition?
4:21:49
specbot
Condition System Concepts: http://www.lispworks.com/reference/HyperSpec/Body/09_a.htm
4:48:45
beach
MichaelRaskin: I think you are right. I need more than one `next' PC value when there is a branch in the code. But I can do that. I just have the table contain either a singleton address or a list of addresses.
7:27:23
aeth
The default type one? It definitely isn't a must-have, but it does prevent increased verbosity when refactoring from certain patterns of DEFUN with DECLARE.
7:49:40
pillton
aeth: Yes. The syntax is quite surprising though (I couldn't think of a better word).
8:17:25
aeth
My exact way to do it is probably not the best way to do it, but my API isn't final so I went with it for now.
8:23:13
aeth
The way it would show up when working with sequences would probably be something like: (define-foo map-two-into! ((destination some-seq) (function function) (seq-1 some-seq) (seq-2 some-seq)) (map-into destination function seq-1 seq-2)) Except, of course, it would be doing something more specific that just happens to match that basic pattern.
8:58:22
beach
I factored the descriptions of the three tables providing support for the debugger STEP-* commands: http://metamodular.com/code-object.pdf
9:43:09
beach
I also updated this document: http://metamodular.com/clordane.pdf (section 1.2.8 on page 4) to reflect the different kinds of possible STEP commands. I added a description of how Clordane accomplishes stepping.
11:04:43
Colleen
attila_lendvai: drmeister said at 2018.05.18 14:56:12: Do you recall how to shut down messages from waf? Specifically when it links or aggregates all of the scraped files? The lines are really long and they cause emacs to pause for many seconds when you try to skip over them.
11:38:40
attila_lendvai
beach: I can see it if I search for 'Terminology' in the pdf on that^ url. I have 3 maches (as opposed to the expected 2)
11:41:09
beach
So there is on in the table of contents, one in the section header, and one on top of a page.
13:26:58
beach
I added a Debugger interactor window and a row of command buttons to the imagined layout of the Clordane windows: http://metamodular.com/clordane-layout.pdf
14:04:43
beach
So for liveness information, what would the user of a debugger want to know? I am thinking at least 1. The current value of the variable. 2. The point in the source code where it was initially created. 3. The points in the source code that may affect its current value. 4. Other points in the source code where the variable is referred to. Anything else?
14:13:15
beach
Right. So that if the user wants to change the value, it will only accept values of the right type.