diff options
author | Andrew Yu <andrew@andrewyu.org> | 2022-10-07 15:22:49 +0200 |
---|---|---|
committer | Andrew Yu <andrew@andrewyu.org> | 2022-10-07 15:22:49 +0200 |
commit | 43128265fa2182a3a157d98f287110b06d13950d (patch) | |
tree | 1f0ded8d16cf9b186c597cfd64313d43e78bffcb | |
parent | 3ef66199e94fa889c2e02b57e3fba7403955ca79 (diff) | |
download | website-43128265fa2182a3a157d98f287110b06d13950d.tar.gz website-43128265fa2182a3a157d98f287110b06d13950d.zip |
Links to repositories.
-rw-r--r-- | index.html | 7 |
1 files changed, 7 insertions, 0 deletions
@@ -23,6 +23,13 @@ Do what the programmer writes. For example, the compiler MUST NOT do GCC-style optimizations such as replacing <code>printf("Hello, world!\n")</code> with <code>puts("Hello, world!")</code> (C example, we'll use our own language when that happens). However, as humans often make mistakes (i.e. it is rarely wanted to use <code>printf</code> instead of <code>puts</code> for printing a single string), linters SHOULD be able to detect that (and more subtle issues like double-free, use-after-free, potential buffer overflows, etc) and offer alternatives. But in no circumstance should the computer do differently than told. </li> </ul> + <h2>Repositories</h2> + <ul> + <li><a href="https://git.andrewyu.org/evosaur/website.git">The Source Code of the Evosaur Website</a></li> + <li><a href="https://git.andrewyu.org/evosaur/development.git">Evosaur Development Scratchpad</a></li> + <li><a href="https://git.andrewyu.org/evosaur/specification.git">The Evosaur Specification</a></li> + <li><a href="https://git.andrewyu.org/evosaur/license.git">Evosaur Copyright, License and (anti-)Patent Lab</a></li> + </ul> <h2>Thoughts</h2> <p> These are incomplete (as in not complete enough to be in a specification of any kind) thoughts that we had. |