|NotNite 8058d7c4e6||il y a 1 an|
|compiler||il y a 1 an|
|examples||il y a 1 an|
|thirdparty||il y a 1 an|
|tools||il y a 1 an|
|vlib||il y a 1 an|
|.gitignore||il y a 1 an|
|CONDUCT.md||il y a 1 an|
|CONTRIBUTING.md||il y a 1 an|
|LICENSE||il y a 1 an|
|Makefile||il y a 1 an|
|README.md||il y a 1 an|
|make.bat||il y a 1 an|
|make_msvc.bat||il y a 1 an|
|make_tests.bat||il y a 1 an|
we should make a fork of vlang called vorelang and make an org for it
- notnite, 2019
vorelang is a fork of the V programming language. it’s intent is to take the hacky code of V, make it more secure, and add some shitposts into the mix while doing so.
vorelang is a for-fun project - we do not accept funds, nor do we plan to actually put effort into this. if you are looking for a stable programming language similar to V or vorelang, try zig I guess.
it is highly recommended to use the makefile. using the batch scripts may lead to bulid environment inconsistencies.
vorelang can be installed the same way as v - clone the repo and run the makefile.
Windows users may also use the batch files in the repo, however we strongly suggest using WSL instead.
there are three compilers of vore you can get, called “stages” here:
there may be problems while trying to build stage1 as mr. v adds syntax into the compiler source that isn’t supported by stage0. Vore is sorry for the problems upstream brings to us.
compiling stage2 exists for users who already have a relatively recent stage1.
git clone https://gitdab.com/vorelang/vorelang.git cd vorelang # when setting v for the first time, use the v target to bootstrap v from # the c compiler make stage1 ./v # you may use a functioning stage1 to build stage2 make stage2 ./v2