summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorLeo Tenenbaum <pommicket@gmail.com>2019-12-16 10:13:49 -0500
committerLeo Tenenbaum <pommicket@gmail.com>2019-12-16 10:13:49 -0500
commit93093f5a220582ade7e51008d6c234a508381089 (patch)
treec871a5b832417bc06a0da7a163db742df4a8394e /docs
parent11dee9f0ce8f4e907379338ace7b808e80efe929 (diff)
updated readme
Diffstat (limited to 'docs')
-rw-r--r--docs/00.html7
-rw-r--r--docs/01.html4
2 files changed, 5 insertions, 6 deletions
diff --git a/docs/00.html b/docs/00.html
index b8c961c..cd0c352 100644
--- a/docs/00.html
+++ b/docs/00.html
@@ -30,7 +30,7 @@ x := 0.0;
when no type is specified, it defaults to an <code>int</code>, whereas <code>0.0</code>
defaults to a <code>float</code>.</p>
-<p>Here are all of toc&rsquo;s builtin types and their ranges of values:</p>
+<p>Here are all of toc's builtin types and their ranges of values:</p>
<ul>
<li><code>int</code> - A 64-bit signed integer (always), -9223372036854775808 to 9223372036854775807</li>
@@ -49,14 +49,13 @@ defaults to a <code>float</code>.</p>
<li><code>char</code> - A character. The specific values are technically platform-dependent, but usually there are 256 of them.</li>
</ul>
-
<p>At the moment, it is not technically guaranteed that <code>f32</code>/<code>float</code> is actually 32-bit and that <code>f64</code> is actually 64-bit; they are platform dependent. Perhaps someday there will be a version of toc which does not compile to C, where that could be guaranteed.</p>
<p>To make declarations constant, use <code>::</code> instead of <code>:</code>. e.g.</p>
<p><code>
-x ::= 5+3;
+x ::= 5+3; <br />
y :: float = 5.123;
</code></p>
-<p>Here, &ldquo;constant&rdquo; means constant at compile time, not read-only as it does in C. One interesting thing about toc is that normal functions can run at compile time, so pretty much any expression is a valid initializer for a constant, e.g. doing <code>x ::= some_function();</code> runs <code>some_function</code> at compile time, not at run time.</p>
+<p>Here, "constant" means constant at compile time, not read-only as it does in C. One interesting thing about toc is that normal functions can run at compile time, so pretty much any expression is a valid initializer for a constant, e.g. doing <code>x ::= some_function();</code> runs <code>some_function</code> at compile time, not at run time.</p>
diff --git a/docs/01.html b/docs/01.html
index 6dce358..633295b 100644
--- a/docs/01.html
+++ b/docs/01.html
@@ -7,7 +7,7 @@ main ::= fn() {
};
</code></p>
-<p>It declares a constant, <code>main</code>, which is a function with an empty body. Note that the syntax for declaring functions is the same as the syntax for declaring constants (it isn&rsquo;t something like <code>fn main() { ... }</code>).</p>
+<p>It declares a constant, <code>main</code>, which is a function with an empty body. Note that the syntax for declaring functions is the same as the syntax for declaring constants (it isn't something like <code>fn main() { ... }</code>).</p>
<p>Assuming you have compiled the compiler (see <code>README.md</code> for instructions about that), you can compile it with</p>
@@ -15,4 +15,4 @@ main ::= fn() {
toc &lt;your filename&gt;
</code></p>
-<p>You will get a file called <code>out.c</code>, which you can then put through your C compiler to get an executable file which does nothing. Congratulations! You&rsquo;ve written your first toc program.</p>
+<p>You will get a file called <code>out.c</code>, which you can then put through your C compiler to get an executable file which does nothing. Congratulations! You've written your first toc program.</p>