Mercurial > vim
diff runtime/doc/vim9.txt @ 23047:29c5f168c6fd
Update runtime files
Commit: https://github.com/vim/vim/commit/23515b4ef7580af8b9d3b964a558ab2007cacda5
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Nov 29 14:36:24 2020 +0100
Update runtime files
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sun, 29 Nov 2020 14:45:04 +0100 |
parents | e7c125224b1a |
children | 285cde4b8d0e |
line wrap: on
line diff
--- a/runtime/doc/vim9.txt +++ b/runtime/doc/vim9.txt @@ -1,4 +1,4 @@ -*vim9.txt* For Vim version 8.2. Last change: 2020 Nov 20 +*vim9.txt* For Vim version 8.2. Last change: 2020 Nov 25 VIM REFERENCE MANUAL by Bram Moolenaar @@ -388,6 +388,9 @@ This will assign "start" and print a lin var result = start :+ print +Note that the colon is not required for the |+cmd| argument: > + edit +6 fname + It is also possible to split a function header over multiple lines, in between arguments: > def MyFunc( @@ -1122,7 +1125,7 @@ are used. That is different, thus it's `:var`. This is used in many languages. The semantics might be slightly different, but it's easily recognized as a declaration. -Using `:const` for constants is common, but the semantics vary. Some +Using `:const` for constants is common, but the semantics varies. Some languages only make the variable immutable, others also make the value immutable. Since "final" is well known from Java for only making the variable immutable we decided to use that. And then `:const` can be used for making @@ -1182,7 +1185,7 @@ text not starting with a number would be considered false. Thus using a string for a condition would often not give an error and be considered false. That is confusing. -In Vim9 type checking is more strict to avoid mistakes. Where a condition is +In Vim9 type checking is stricter to avoid mistakes. Where a condition is used, e.g. with the `:if` command and the `||` operator, only boolean-like values are accepted: true: `true`, `v:true`, `1`, `0 < 9`