vieter-v
/
v
2
0
Fork 0
Code Issues Pull Requests Releases Activity

doc: use `v new` instead of `v create`

pull/5385/head
Delyan Angelov 2020-06-14 21:20:26 +03:00
parent 4e1a09c9f5
commit c874a22b3b
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/docs.md
View File

@ -1567,7 +1567,7 @@ NB: Each flag must go on its own line (for now)
You can also include C code directly in your V module. For example, let's say that your C code is located in a folder named 'c' inside your module folder. Then: You can also include C code directly in your V module. For example, let's say that your C code is located in a folder named 'c' inside your module folder. Then:
* Put a v.mod file inside the toplevel folder of your module (if you * Put a v.mod file inside the toplevel folder of your module (if you
created your module with `v create` you already have v.mod file). For created your module with `v new` you already have v.mod file). For
example: example:
```v ```v
Module { Module {

2
vlib/v/tests/project_with_modules_having_submodules/v.mod
View File

@ -2,6 +2,6 @@
Module { Module {
name: 'project_with_modules_having_submodules', name: 'project_with_modules_having_submodules',
description: 'This project was created with `v create` to prevent regressions with the way V module import lookup works.', description: 'This project was created with `v new` to prevent regressions with the way V module import lookup works.',
dependencies: [] dependencies: []
} }