From eef73edb57b77dc85ad3f608f790e96026076e60 Mon Sep 17 00:00:00 2001 From: Alexander Medvednikov Date: Wed, 30 Dec 2020 02:27:05 +0100 Subject: [PATCH] doc: remove ... placeholder that caused confusion --- doc/docs.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/docs.md b/doc/docs.md index 1725409d98..47f09377de 100644 --- a/doc/docs.md +++ b/doc/docs.md @@ -318,7 +318,7 @@ import gg fn draw(ctx &gg.Context) { gg := ctx.parent.get_ui().gg - gg.draw_rect(...) + gg.draw_rect(10, 10, 100, 50) } ``` @@ -2971,11 +2971,11 @@ If a file has an environment-specific suffix, it will only be compiled for that - `.c.v` => will be used only by the C backend. These files can contain C. code. - `.x64.v` => will be used only by V's x64 backend. - `_nix.c.v` => will be used only on Unix systems (non Windows). -- `_${os}.c.v` => will be used only on the specific `os` system. +- `_${os}.c.v` => will be used only on the specific `os` system. For example, `_windows.c.v` will be used only when compiling on Windows, or with `-os windows`. -- `_default.c.v` => will be used only if there is NOT a more specific platform file. -For example, if you have both `file_linux.c.v` and `file_default.c.v`, -and you are compiling for linux, then only `file_linux.c.v` will be used, +- `_default.c.v` => will be used only if there is NOT a more specific platform file. +For example, if you have both `file_linux.c.v` and `file_default.c.v`, +and you are compiling for linux, then only `file_linux.c.v` will be used, and `file_default.c.v` will be ignored. Here is a more complete example: @@ -3006,7 +3006,7 @@ const ( message = 'Hello windows' ) With the example above: - when you compile for windows, you will get 'Hello windows' - when you compile for linux, you will get 'Hello linux' -- when you compile for any other platform, you will get the +- when you compile for any other platform, you will get the non specific 'Hello world' message. ## Compile time pseudo variables