Skip to content

Commit 547ee0f

Browse files
committed
typo and paragraphs
1 parent ca4dbbf commit 547ee0f

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

sindarin/byexample.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -65,14 +65,14 @@ sindarin stepUntil: [
6565
sindarin isMessageSend and: [sindarin selector = #addLast:]].
6666
sindarin node sourceCode. "'array size'"
6767
```
68-
Notice the following points:
69-
- We first test if we are in the context of a message send, using `isMessageSend`.
68+
We first test if we are in the context of a message send, using `isMessageSend`.
7069
We must satisfy this condition before trying to access the `selector` of the message being sent, else we might not be in such context and an exception will be raised.
71-
- The `sourceCode` interface returns `"'array size'"`, i.e., the next instruction to be executed, supposedly within the body of the `addLast:` method.
70+
71+
The `sourceCode` interface returns `"'array size'"`, i.e., the next instruction to be executed, supposedly within the body of the `addLast:` method but we do not have enough information.
7272
This interface is not really adapted to visualize the actual executing source code.
7373
For a better perspective, we can inspect the `sindarin` variable, which opens a minimal debugger that allows us to visualize the debugged code (fig. *@fig:sindarin-inspector@*). This minimal debugger exposes the Sindarin API through a graphical user interface, as well as views on the debugged execution and its state.
7474

75-
![Sindarin advanced debugger menu.](graphics/sindarin-inspector.drawio.png label=fig:sindarin-inspector)
75+
![The Sindarin minimal debugger.](graphics/sindarin-inspector.drawio.png label=fig:sindarin-inspector)
7676

7777

7878
### Variable breakpoint example

0 commit comments

Comments
 (0)