diff options
| author | Marshall Lochbaum <mwlochbaum@gmail.com> | 2022-06-11 20:08:12 -0400 |
|---|---|---|
| committer | Marshall Lochbaum <mwlochbaum@gmail.com> | 2022-06-11 20:08:12 -0400 |
| commit | b6bcf214e638fd36ef7d76c9f573a84e6e016482 (patch) | |
| tree | a435e4f0afed7266b868798e51b792c4600fabe1 /doc/assert.md | |
| parent | 383298b70274c5ac22eb2100aad7f6cd8eeca02d (diff) | |
Nothing but edits yet again
Diffstat (limited to 'doc/assert.md')
| -rw-r--r-- | doc/assert.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/assert.md b/doc/assert.md index f193be21..14e4cf72 100644 --- a/doc/assert.md +++ b/doc/assert.md @@ -38,6 +38,6 @@ The `Catch` modifier allows you to handle errors in BQN (at present, it's the on 0.5 ⌽⎊⊣ ↕6 # A two-argument example -Catch doesn't know anything about what an error *is*, just whether there was one or not. In fact, the idea of error message doesn't feature at all in core BQN: it's purely part of the language environment. So you need a system value to access information about the error. Right now the only one is `•CurrentError`, which is a function that returns a message for the error currently caught (if any). +Catch doesn't know anything about what an error *is*, just whether there was one or not. In fact, the idea of an error message doesn't feature at all in core BQN: it's purely part of the language environment. So you need a system value to access information about the error. Right now the only one is `•CurrentError`, which is a function that returns a message for the error currently caught (if any). ⌽⎊•CurrentError 2 |