Yasuhiro Matsumoto wrote:
> # strange parse of binary format
> ```
> :echo 0b19
> 1 9
> ```
>
> # strange token separator
> ```
> :let b99 = 'vim'
> :echo 0b99
> 0 vim
> ```
> ```
> :function! B99()
> : return 'vim'
> :endfunction
> :echo 0B99()
> 0 vim
> ```
>
> # storage parse of hex format
> ```
> :let xZZ = 'vim'
> :echo 0xZZ
> 0 vim
> ```
>
> ```
> :let km = 'kilometer'
> :echo 100km
> 100 kilometer
> ```
>
> # storage parse of JSON string
>
> ```
> :echo json_decode('"\u111Z"')
> d Z
> ```
>
> The all must be an error.
Well, they look like an error, but the parsing of the :echo command has
always been very forgiving. I've seen users abuse that and omit spaces,
just because they can and they don't care about it being messy.
Turning these into an error is likely to break something. Perhaps not
for the examples you give here, which are obviously bad, but where it
makes more sense. The "100km" one is actually useful.
The JSON one is a bit strange. Oh, I actually get "dZ", no space.
--
Are leaders born or made? And if they're made, can we return them under
warranty?
(Scott Adams - The Dilbert principle)
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
