From aac24c2c43a8047ceb41f1b34336ba2ed8064569 Mon Sep 17 00:00:00 2001 From: Kimplul Date: Wed, 23 Oct 2024 18:31:01 +0300 Subject: slightly better wording in README --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 5fa741a..0eb2f84 100644 --- a/README.md +++ b/README.md @@ -58,10 +58,10 @@ if (< 10 20) \ There are two 'builtins' beyond what GNU Guile provides (all GNU Guile functions can be called as commands), namely `get` and `expand`. They're effectively the identity commands, i.e. `get` returns the value that was passed into it, and -`expand` expands a macro as if it didn't exist. These are useful because, again, -*literally* everythin is a command, so if you want to return a value you can't -just write `arg` as the last element of a `(begin ...)` or whatever, because -that value will be interpreted as a command. Same thing with macros. +`expand` expands a macro as if `expand` weren't there. These are useful because, +again, *literally* everythin is a command, so if you want to return a value you +can't just write `arg` as the last element of a `(begin ...)` or whatever, +because that value will be interpreted as a command. Same thing with macros. Note that `values` is effectively the same thing as `get`, but I think `get` has a nicer symmetry with `let`/`set`. `macroexpand` is (maybe somewhat surprisingly) not equivalent to `expand`, as `macroexpand` can't handle -- cgit v1.2.3