Recently Written · git

LispBrain

The best Brainfuck debugger available, if you know how the Common Lisp debugger works. Uses Common Lisp's ease of debugging to make debugging Brainfuck code easy. Almost entirely useless.

git clone https://github.com/equwal/LispBrain

Log | Files | Refs


commit f17d1edeebe84c559b89ba6a362b7bf4b888f1f0
Spenser Truex <spensertruexonline@gmail.com>
2018-03-06 00:24:45 -0300

Update README.md
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
index 133cfdb..e706f4c 100644
--- a/README.md
+++ b/README.md
@@ -47,7 +47,7 @@ If you are unable to find where the ASDF load directory is, you may choose to lo
 
 In Allegro common lisp one must first use `(require :asdf)` before executing any other commands in order to activate the preinstalled ASDF system.
 # How to Use:
-If everything runs smoothly you will be ready to Brainfuck. If there are issues then please *let it be known*. Now one must chooses between the `brain:fuck` and the `#F` notation when using the REPL. The `#F` notation is more concise but does not allow any whitespaces or closing parenthesis in the Brainfuck code, while the `brain:fuck` notation allows any character except for an unescaped literal quote `"`, or an unescaped literal backward slash `\` inside of the Brainfuck code. Below they are both shown:
+If everything runs smoothly you will be ready to Brainfuck. If there are issues then please *let it be known*. Now one must choose between the `brain:fuck` and the `#F` notation when using the REPL. The `#F` notation is more concise but does not allow any whitespaces or closing parenthesis in the Brainfuck code, while the `brain:fuck` notation allows any character except for an unescaped literal quote `"`, or an unescaped literal backward slash `\` inside of the Brainfuck code. Below they are both shown:
 ```
 > (brain:fuck ".+[.+] Please escape your \" and \\ characters!")
 "�