authorgravatar for andrew@ziglang.orgAndrew Kelley <andrew@ziglang.org> 2015-11-24 23:56:35-07:00
committergravatar for andrew@ziglang.orgAndrew Kelley <andrew@ziglang.org> 2015-11-24 23:56:35-07:00
log4fe366dfa6e58d7e0c159a5e864fec56499cc888
tree6413fd80176454aa2ab191c420432ed125a7e3b7
parent09f68c7c339075183c67c56149620c6970b6842a

cleanup

2 files changed, 0 insertions(+), 11 deletions(-)

CMakeLists.txt-2
...@@ -20,8 +20,6 @@ include_directories(...@@ -20,8 +20,6 @@ include_directories(
20 ${CMAKE_BINARY_DIR}20 ${CMAKE_BINARY_DIR}
21)21)
2222
23set(GRAMMAR_TXT "${CMAKE_BINARY_DIR}/simple.txt")
24
25set(ZIG_SOURCES23set(ZIG_SOURCES
26 "${CMAKE_SOURCE_DIR}/src/buffer.cpp"24 "${CMAKE_SOURCE_DIR}/src/buffer.cpp"
27 "${CMAKE_SOURCE_DIR}/src/error.cpp"25 "${CMAKE_SOURCE_DIR}/src/error.cpp"
README.md-9
...@@ -4,15 +4,6 @@ An experiment in writing a low-level programming language with the intent to...@@ -4,15 +4,6 @@ An experiment in writing a low-level programming language with the intent to
4replace C. Zig intends to be a small language, yet powerful enough to write4replace C. Zig intends to be a small language, yet powerful enough to write
5readable, safe, optimal, and concise code to solve any computing problem.5readable, safe, optimal, and concise code to solve any computing problem.
66
7## Design Principles
8
9 * Never compromise power or performance.
10 * Keep the language small and easy to understand. C programmers should pretty
11 much be able to understand Zig source code without learning anything about
12 Zig.
13 * Interoperability with C is crucial. Using C libraries should not require
14 "Zig bindings".
15
16## Goals7## Goals
178
18 * Ability to run arbitrary code at compile time and generate code.9 * Ability to run arbitrary code at compile time and generate code.