| author | |
| committer | |
| log | 79400bfdfd1e90cf3a4d09f32de965b13796a44d |
| tree | 352f583af59ecc7b38431554ddc6d665e9e44222 |
| parent | 6c3a56a7ffd5a2ec5119447aa81dce9bf6ec1319 |
2 files changed, 10 insertions(+), 3 deletions(-)
README.md+8-1| ... | ... | @@ -106,13 +106,20 @@ libc. Create demo games using Zig. |
| 106 | 106 | These compile tools must be available on your system and are used to build |
| 107 | 107 | the Zig compiler itself: |
| 108 | 108 | |
| 109 | ##### POSIX | |
| 110 | ||
| 109 | 111 | * gcc >= 5.0.0 or clang >= 3.6.0 |
| 110 | 112 | * cmake >= 2.8.5 |
| 111 | 113 | |
| 114 | ##### Windows | |
| 115 | ||
| 116 | * Microsoft Visual Studio 2015 | |
| 117 | ||
| 112 | 118 | #### Library Dependencies |
| 113 | 119 | |
| 114 | 120 | These libraries must be installed on your system, with the development files |
| 115 | available. The Zig compiler links against them. | |
| 121 | available. The Zig compiler links against them. You have to use the same | |
| 122 | compiler for these libraries as you do to compile Zig. | |
| 116 | 123 | |
| 117 | 124 | * LLVM, Clang, and LLD libraries == 5.x |
| 118 | 125 |
doc/semantic_analysis.md+2-2| ... | ... | @@ -6,8 +6,8 @@ choose to add more files to the compilation, for example bootstrap.zig which |
| 6 | 6 | contains the code that calls main. |
| 7 | 7 | |
| 8 | 8 | Our goal now is to treat everything that is marked with the `export` keyword |
| 9 | as a root node, and then then parse and semantically analyze as little as | |
| 10 | possible in order to fulfill these exports. | |
| 9 | as a root node, and then parse and semantically analyze as little as possible | |
| 10 | in order to fulfill these exports. | |
| 11 | 11 | |
| 12 | 12 | So, some parts of the code very well may have uncaught semantic errors, but as |
| 13 | 13 | long as the code is not referenced in any way, the compiler will not complain |