first steps to explicit channels for thread communication; added mainThreadId
This commit is contained in:
parent
fe5df368c1
commit
42e6130b2c
16 changed files with 155 additions and 71 deletions
12
doc/endb.txt
12
doc/endb.txt
|
|
@ -6,10 +6,10 @@
|
|||
:Version: |nimrodversion|
|
||||
|
||||
.. contents::
|
||||
|
||||
|
||||
**Note:** ENDB has not been maintained/tested since several versions. Help if
|
||||
you want this debugger to survive.
|
||||
|
||||
|
||||
**Note:** ENDB has not been maintained/tested since several versions. Help if
|
||||
you want this debugger to survive.
|
||||
|
||||
Nimrod comes with a platform independant debugger -
|
||||
the `Embedded Nimrod Debugger`:idx: (`ENDB`:idx:). The debugger is
|
||||
|
|
@ -57,7 +57,7 @@ Executing Commands
|
|||
Continue execution until the next breakpoint.
|
||||
|
||||
``i``, ``ignore``
|
||||
Continue execution, ignore all breakpoints. This is effectively quitting
|
||||
Continue execution, ignore all breakpoints. This effectively quits
|
||||
the debugger and runs the program until it finishes.
|
||||
|
||||
|
||||
|
|
@ -143,7 +143,7 @@ Data Display Commands
|
|||
painfully slow, the debugger uses a *maximal display depth* concept for
|
||||
displaying.
|
||||
|
||||
You can alter the *maximal display depth* with the ``maxdisplay``
|
||||
You can alter the maximal display depth with the ``maxdisplay``
|
||||
command.
|
||||
|
||||
``maxdisplay`` <natural>
|
||||
|
|
|
|||
|
|
@ -3153,7 +3153,7 @@ over *fine grained* concurrency.
|
|||
Threads and exceptions
|
||||
----------------------
|
||||
|
||||
The interaction between threads and exception is simple: A *handled* exception
|
||||
The interaction between threads and exceptions is simple: A *handled* exception
|
||||
in one thread cannot affect any other thread. However, an *unhandled*
|
||||
exception in one thread terminates the whole *process*!
|
||||
|
||||
|
|
|
|||
|
|
@ -200,7 +200,7 @@ for any type:
|
|||
echo("abc".len) # is the same as echo(len("abc"))
|
||||
echo("abc".toUpper())
|
||||
echo({'a', 'b', 'c'}.card)
|
||||
stdout.writeln("Hallo") # the same as write(stdout, "Hallo")
|
||||
stdout.writeln("Hallo") # the same as writeln(stdout, "Hallo")
|
||||
|
||||
(Another way to look at the method call syntax is that it provides the missing
|
||||
postfix notation.)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue