On 30/03/14 22:58, ZyX wrote:
This is not good. These inconsistencies need to be fixed.
String indexing*must* not fixed. As I said there is a number of plugins that
need*exactly* bytes: any plugin implementing hash function. char2nr(s[i]) is
guaranteed to return a value between 0x00 and 0xFF (inclusive) (0x00 is
returned only if s[i] is an empty string).
Thanks for your insights. It's not perfect but it's much better than I was
originally thinking.
I didn't say that string indexing has to be fixed. I said the
inconsistencies
had to be fixed. There is a difference.
The inconsistency of looking at this:
1) "this is a test"
and this:
2) "こんにちわ世界"
and having to say "(1) is a string, but (2) is a byte sequence" just because
I live in a part of the world that doesn't use English (8-bit
characters) is an
inconsistency that needs to be addressed. Any reasonable language that
provides string constants should treat everything in between double quotes
consistently.
The fact we have plug-ins that operate only in byte mode or rely on that
particular behaviour is an issue that prevents the necessary changes from
being applied cleanly and easily.
Again, thanks for your insights. Very useful.
--
--
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.
