Skip to content

Commit

Permalink
[MINOR] Small clarifications and fixed typos in the docs.
Browse files Browse the repository at this point in the history
  • Loading branch information
pdamme committed Apr 5, 2024
1 parent 5de5748 commit 67e2705
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 4 deletions.
5 changes: 2 additions & 3 deletions doc/DaphneDSL/Builtins.md
Original file line number Diff line number Diff line change
Expand Up @@ -80,9 +80,8 @@ DaphneDSL's built-in functions can be categorized as follows:

- **`seq`**`(from:scalar, to:scalar, inc:scalar)`

Generates a column *(n x 1)* matrix containing an arithmetic sequence of values starting at `from`, going through `to`, in increments of `inc`.
Generates a column matrix containing an arithmetic sequence of values starting at `from`, going through `to`, in increments of `inc`.
Note that `from` may be greater than `to`, and `inc` may be negative.
If `inc` does not lead from `from` to `to`, the result will be an empty column matrix; however, `inc` must not be zero or NaN.

## Matrix/frame dimensions

Expand Down Expand Up @@ -145,7 +144,7 @@ The following built-in functions all follow the same scheme:
## Elementwise binary

DaphneDSL supports various elementwise binary operations.
Some of those can be used through *operators in infix notation*, e.g., `+`; and some through *built-in functions*.
Some of those can be used through *operators in infix notation*, e.g., `+`; and some through *built-in functions*, e.g., `log()`.
Some operations even support both, e.g., `pow(a, b)` and `a^b` have the same semantics.

The built-in functions all follow the same scheme:
Expand Down
2 changes: 1 addition & 1 deletion doc/development/WriteDocs.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ Please write clean markdown code to ensure a proper parsing by the tools used to
### Links

* With `[<link-name>](<link-url/path>)` you can link to other files in the repo
* Write links to other markdown files or source code files/diretories so that they work locally / in the github repository
* Write links to other markdown files or source code files/directories so that they work locally / in the github repository
* Do not use relative links like `../BuildingDaphne.md`
* Always use absolute paths relative to the repo root like `/doc/development/BuildingDaphne.md`
* The Links/URLs will be altered in order to work on the rendered HTML page as well
Expand Down

0 comments on commit 67e2705

Please sign in to comment.