> /*
> * Version of strchr() and strrchr() that handle unsigned char strings
> * with characters from 128 to 255 correctly. It also doesn't return a
> * pointer to the NUL at the end of the string.
> */
> char_u *
> vim_strchr(string, c)
> char_u *string;
> int c;
> {
> char_u *p;
> int b;
>
> p = string;
> #ifdef FEAT_MBYTE
> if (enc_utf8 && c >= 0x80)
> {
> --->8---
> etc.
Well, honestly, what percentage of C programmers are using the "old
style" function declaration? Of course if you want to do something and
you want to cover all possible cases, you end up never doing that
thing... I think vim should concentrate on evolution and not on
supporting very old things. If it would happen that somebody
exceptionally needs very old features, then he/she could fire up an
old version of the tool...
So, with the "contemporary version" of C declaration, the trivial algo
I mentioned should work..
However you made a good point with your example, as I did not think
that comments before a function definition normally belong to the
function, so they should be part of the function text object...
rgrds,
mobi phil
being mobile, but including technology
http://mobiphil.com
--
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
