clean up: remove redundant spaces

pull/739/head^2
shamofu 2019-06-30 01:05:57 +09:00 committed by Alexander Medvednikov
parent 7eab373922
commit 18082274ca
4 changed files with 19 additions and 22 deletions

View File

@ -7,15 +7,15 @@ matrix:
addons: addons:
apt: apt:
sources: sources:
- ubuntu-toolchain-r-test - ubuntu-toolchain-r-test
packages: packages:
- gcc-5 - gcc-5
- g++-5 - g++-5
- make - make
- libglfw3 - libglfw3
- libglfw3-dev - libglfw3-dev
- libfreetype6-dev - libfreetype6-dev
- libcurl3-dev - libcurl3-dev
- os: windows - os: windows
language: sh language: sh
filter_secrets: false filter_secrets: false
@ -24,8 +24,8 @@ matrix:
addons: addons:
homebrew: homebrew:
packages: packages:
- freetype - freetype
- glfw - glfw
#env: #env:
# - MATRIX_EVAL="brew install freetype glfw" # - MATRIX_EVAL="brew install freetype glfw"
script: script:
@ -41,4 +41,3 @@ script:
- export VROOT=$(pwd) - export VROOT=$(pwd)
- make - make
- make test - make test

View File

@ -1,7 +1,7 @@
# 0.1.8 # 0.1.8
- Single file programs without `fn main` now work as expected. - Single file programs without `fn main` now work as expected.
- REPL has been fixed: it now supports imports, consts, function definitions, etc. - REPL has been fixed: it now supports imports, consts, function definitions, etc.
# 0.1.7 # 0.1.7

View File

@ -32,8 +32,6 @@ It has only 8 files (soon to be 7):
8. `json.v` defines the json code generation. This file will be removed once V supports comptime code generation, and it will be possible to do this using the language's tools. 8. `json.v` defines the json code generation. This file will be removed once V supports comptime code generation, and it will be possible to do this using the language's tools.
9. `x64/` is the directory with all the machine code generation logic. It will be available in early July. Obviously this is the most complex part of the compiler. It defines a set of functions that translate assembly instructions to machine code, it builds complicated binaries from scratch byte by byte. It manually builds all headers, segments, sections, symtable, relocations, etc. Right now it only has basic support of the x64 platform/Mach-O format, and it can only generate `.o` files, which then have to be linked with `lld`. 9. `x64/` is the directory with all the machine code generation logic. It will be available in early July. Obviously this is the most complex part of the compiler. It defines a set of functions that translate assembly instructions to machine code, it builds complicated binaries from scratch byte by byte. It manually builds all headers, segments, sections, symtable, relocations, etc. Right now it only has basic support of the x64 platform/Mach-O format, and it can only generate `.o` files, which then have to be linked with `lld`.
The rest of the directories are vlib modules: `builtin/` (strings, arrays, maps), `time/`, `os/`, etc. Their documentation is pretty clear. The rest of the directories are vlib modules: `builtin/` (strings, arrays, maps), `time/`, `os/`, etc. Their documentation is pretty clear.

View File

@ -3,18 +3,18 @@ all: clean v
v: v.c v: v.c
cc -std=gnu11 -w -o v v.c cc -std=gnu11 -w -o v v.c
./v -o v compiler ./v -o v compiler
rm v.c rm v.c
v.c: v.c:
curl -Os https://raw.githubusercontent.com/vlang/vc/master/v.c curl -Os https://raw.githubusercontent.com/vlang/vc/master/v.c
test: v test: v
./v -prod -o vprod compiler # Test prod build ./v -prod -o vprod compiler # Test prod build
echo "Running V tests..." echo "Running V tests..."
find . -name '*_test.v' -print0 | xargs -0 -n1 ./v find . -name '*_test.v' -print0 | xargs -0 -n1 ./v
echo "Building V examples..." echo "Building V examples..."
find examples -name '*.v' -print0 | xargs -0 -n1 ./v find examples -name '*.v' -print0 | xargs -0 -n1 ./v
clean: clean:
-rm -f v.c v vprod -rm -f v.c v vprod