2019-06-28 01:47:55 +03:00
# The V Programming Language 0.1.x
2019-06-22 21:22:41 +03:00
2019-07-22 13:16:24 +03:00
[![Build Status ](https://travis-ci.org/vlang/v.svg?branch=master )](https://travis-ci.org/vlang/v)
2019-08-20 17:29:06 +03:00
< a href = 'https://patreon.com/vlang' > < img src = 'https://img.shields.io/endpoint.svg?url=https%3A%2F%2Fshieldsio-patreon.herokuapp.com%2Fvlang%2Fpledges&style=for-the-badge' height = '20' > < / a >
2019-06-25 13:27:06 +03:00
2019-06-22 21:22:41 +03:00
https://vlang.io
Documentation: https://vlang.io/docs
Twitter: https://twitter.com/v_language
2019-06-24 03:11:26 +03:00
Discord (primary community): https://discord.gg/n7c74HM
2019-06-24 03:04:58 +03:00
2019-06-23 17:13:56 +03:00
Installing V: https://github.com/vlang/v#installing-v-from-source
2019-06-22 21:22:41 +03:00
2019-06-24 17:04:19 +03:00
## Key Features of V
2019-08-12 11:00:29 +03:00
- Simplicity: the language can be learned in less than an hour
2019-08-27 04:17:50 +03:00
- Fast compilation: ~100k - 1.2 million loc/s
2019-06-24 17:07:41 +03:00
- Easy to develop: V compiles itself in less than a second
2019-08-12 11:00:29 +03:00
- Performance: within 3% of C
2019-06-28 02:54:42 +03:00
- Safety: no null, no globals, no undefined behavior, immutability by default
2019-06-24 17:04:19 +03:00
- C to V translation
2019-06-24 17:36:30 +03:00
- Hot code reloading
2019-06-24 17:04:19 +03:00
- Powerful UI and graphics libraries
- Easy cross compilation
- REPL
2019-08-20 17:35:11 +03:00
- Built-in ORM
2019-06-24 17:04:19 +03:00
2019-08-27 19:35:48 +03:00
V 1.0 release is planned for December 2019. Right now V is in an alpha stage.
2019-06-24 17:04:19 +03:00
2019-06-25 14:16:48 +03:00
## Notes
2019-06-25 13:44:56 +03:00
The compilation is temporarily slower for this release:
2019-06-25 06:46:45 +03:00
2019-06-30 16:26:03 +03:00
- Debug builds are used (use `./v -prod -o v compiler` to get faster compilation).
2019-06-26 16:23:59 +03:00
- vlib is recompiled with every program you build.
2019-06-25 13:05:00 +03:00
- The new formatter runs on every single token and slows the compiler down by ~20%. This will be taken care of.
2019-06-25 14:16:48 +03:00
2019-06-22 21:22:41 +03:00
2019-07-23 01:31:43 +03:00
2019-06-22 21:22:41 +03:00
## Installing V from source
2019-07-24 01:09:56 +03:00
### Linux, macOS, Windows, *BSD, WSL, Android, Raspbian
2019-06-22 21:22:41 +03:00
2019-06-25 16:14:19 +03:00
2019-06-22 21:22:41 +03:00
```bash
2019-06-25 03:02:05 +03:00
git clone https://github.com/vlang/v
2019-06-29 13:58:52 +03:00
cd v
2019-06-23 12:44:40 +03:00
make
2019-06-26 00:02:25 +03:00
```
2019-07-12 16:58:10 +03:00
2019-07-13 13:49:55 +03:00
That's it! Now you have a V executable at `[path to V repo]/v` . `[path to V repo]` can be anywhere.
2019-07-12 16:58:10 +03:00
### C compiler
2019-08-12 10:54:35 +03:00
You'll need Clang or GCC. If you are doing development, you most likely already have it installed.
2019-07-12 16:58:10 +03:00
2019-08-12 10:54:35 +03:00
On macOS run `xcode-select --install` if you don't have XCode or XCode tools.
2019-07-12 16:58:10 +03:00
On Windows follow these instructions: [github.com/vlang/v/wiki/Installing-a-C-compiler-on-Windows ](https://github.com/vlang/v/wiki/Installing-a-C-compiler-on-Windows )
2019-06-22 21:22:41 +03:00
2019-07-12 16:58:10 +03:00
### Symlinking and updates
2019-06-23 14:27:43 +03:00
2019-08-12 10:49:20 +03:00
You can create a `/usr/local/bin/v` symlink so that V is globally available:
2019-06-22 21:22:41 +03:00
```
2019-08-27 19:35:48 +03:00
sudo v symlink
2019-06-22 21:22:41 +03:00
```
2019-06-27 23:32:29 +03:00
V is being constantly updated. To update V, simply run
```
2019-07-31 05:53:24 +03:00
v up
2019-06-27 23:32:29 +03:00
```
2019-08-27 04:17:50 +03:00
### Docker
2019-07-23 03:41:55 +03:00
```bash
git clone https://github.com/vlang/v
cd v
docker build -t vlang .
docker run --rm -it vlang:latest
v
```
2019-06-27 23:32:29 +03:00
2019-07-04 13:36:42 +03:00
2019-06-22 21:22:41 +03:00
2019-08-12 10:54:35 +03:00
### Testing and running the examples
Make sure V can compile itself:
2019-06-22 21:22:41 +03:00
```
2019-08-12 10:54:35 +03:00
v -o v compiler
```
2019-06-22 21:22:41 +03:00
2019-08-12 10:54:35 +03:00
```
2019-06-26 18:58:59 +03:00
$ v
2019-06-30 16:26:03 +03:00
V 0.1.x
2019-06-22 21:22:41 +03:00
Use Ctrl-D to exit
>>> println('hello world')
hello world
>>>
```
```
2019-08-12 11:00:29 +03:00
cd examples
2019-06-26 19:04:10 +03:00
v hello_world.v & & ./hello_world # or simply
v run hello_world.v # this builds the program and runs it right away
2019-06-22 21:22:41 +03:00
v word_counter.v & & ./word_counter cinderella.txt
2019-06-24 18:13:02 +03:00
v run news_fetcher.v
2019-07-22 05:57:55 +03:00
v run tetris/tetris.v
2019-06-22 21:22:41 +03:00
```
2019-06-23 17:16:55 +03:00
< img src = 'https://raw.githubusercontent.com/vlang/v/master/examples/tetris/screenshot.png' width = 300 >
2019-06-22 21:22:41 +03:00
In order to build Tetris and anything else using the graphics module, you will need to install glfw and freetype.
2019-08-02 03:13:33 +03:00
```
v install glfw
```
2019-08-27 04:17:50 +03:00
If you plan to use the http package, you also need to install OpenSSL on non-Windows systems.
2019-06-22 21:22:41 +03:00
```
2019-06-26 19:04:10 +03:00
macOS:
2019-08-10 12:51:55 +03:00
brew install glfw freetype openssl
2019-06-25 21:48:34 +03:00
2019-08-09 11:17:56 +03:00
Debian/Ubuntu:
2019-08-12 09:14:48 +03:00
sudo apt install libglfw3 libglfw3-dev libfreetype6-dev libssl-dev
2019-06-22 21:22:41 +03:00
2019-08-09 11:17:56 +03:00
Arch/Manjaro:
2019-08-10 12:51:55 +03:00
sudo pacman -S glfw-x11 freetype2
2019-08-09 11:17:56 +03:00
Fedora:
2019-08-10 12:51:55 +03:00
sudo dnf install glfw glfw-devel freetype-devel
2019-06-22 21:22:41 +03:00
```
2019-06-24 19:53:22 +03:00
2019-08-10 12:51:55 +03:00
glfw dependency will be removed soon.
2019-07-22 17:07:37 +03:00
2019-08-12 10:54:35 +03:00
## Contributing
Code structure:
2019-07-22 17:07:37 +03:00
https://github.com/vlang/v/blob/master/CONTRIBUTING.md
2019-08-12 10:54:35 +03:00
If you introduce a breaking change and rebuild V, you will no longer be able to use V to build itself. So it's a good idea to make a backup copy of a working compiler executable.