## toc `toc` is a language which compiles to C. --- ### About `toc` is currently in development. **It is not a stable language, and there are almost definitely bugs right now.** I would recommend against using it for anything big or important. Many parts of it may change in the future. `toc` improves on C's syntax (and semantics) in many ways, To declare `x` as an integer and set it to 5, you can do: ``` x := 5; // Declare x and set x to 5 (infer type) x : int = 5; // Explicitly make the type int. x : int; x = 5; // Declare x as an integer, then set it to 5. ``` `toc` is statically typed and has many of C's features, but it is nearly as fast in theory. See `docs` for more information (in progress). `tests` has some test programs written in `toc`. To compile the compiler on a Unix-y system, just run `./build.sh release`. You can supply a compiler by running `CC=tcc ./build.sh release`, or build it in debug mode without the `release`. To disable compile time foreign function support (which you will need to do if you don't have ffcall/dl), prefix this with `COMPILE_TIME_FOREIGN_FN_SUPPORT=no`. On other systems, you can just compile main.c with a C compiler. `toc` uses several C99 and a couple of C11 features, so it might not work on all compilers. But it does compile on quite a few, including `clang`, `gcc`, and `tcc`. It can also be compiled as if it were C++, so, MSVC and `g++` can also compile it (it does rely on implicit casting of `void *` though). The *outputted* code should be C99-compliant. #### Why it compiles to C `toc` compiles to C. Here are some reasons why: - Speed. C is one of the most performant programming languages out there. It also has compilers which are very good at optimizing (better than anything I could write). - Portability. C is probably the most portable language. It has existed for >30 years and can run on practically anything. Furthermore, all major languages nowadays can call functions written in C. --- ### `toc` Compiler Source Code Most of the source code for the `toc` compiler is licensed under the GNU General Public License, version 3, and the rest (some small general utilities) is in the public domain. Each source file begins with a comment explaining its license. See `LICENSE` for the GNU General Public License. `toc` is written in C, for speed and portability. It has no dependencies, other than the C runtime library. If you want to be able to call external C functions at compile time, however, you will need `libffcall` and `libdl` (so this is only currently supported on Unix-y systems). #### Build system `toc` is set up as a unity build, meaning that there is only one translation unit. So, `main.c` `#include`s `toc.c`, which `#include`s all of `toc`'s files. ##### Why? This improves compilation speeds (especially from scratch), since you don't have to include headers a bunch of times for each translation unit. This is more of a problem in C++, where, for example, doing `#include ` ends up turning into 25,000 lines after preprocessing. All of toc's source code, which includes most of the C standard library, at the time of this writing (Dec 2019) is only 22,000 lines after preprocessing; imagine including all of that once for each translation unit which includes `map`. It also obviates the need for fancy build systems like CMake. #### New features Here are all the C99 features which `toc` depends on (I might have forgotten some...): - Declare anywhere - `inttypes.h` - Non-constant struct literal initializers (e.g. `int x[2] = {y, z};`) - Flexible array members - `snprintf` And here are all of its C11 features: - Anonymous structures/unions - `max_align_t` - It can still compile without this, and will almost definitely work, but it won't technically be standard-compliant #### More See `main.c` for a bit more information. --- ### Version history Here are the major versions of `toc`.
VersionDescriptionDate
0.0Initial version.2019 Dec 6
0.1Constant parameter inference.2019 Dec 15
0.2Foreign functions and #include.2020 Jan 29
--- ### Report a bug If you find a bug, you can report it through [GitHub's issue tracker](https://github.com/pommicket/toc/issues), or by emailing pommicket@gmail.com. Just send me the `toc` source code which results in the bug, and I'll try to fix it.