воскресенье, 8 апреля 2012 г., 23:14:43 UTC+4 пользователь Luis Carvalho
написал:
> > Yes, there was a copy-paste issue in if_lua.c (their creators copy-pasted
> > from eval.c, I chose to purge "static" from declaration there and add a
> > prototype to eval.pro). Fixed in one of recent commits (removed this
> > function from if_lua).
>
> Yes, that's basically the reason why I haven't included funcrefs in if_lua: I
> didn't want to touch eval.c more than necessary, but call_func (and
> function_exists, if I recall correctly) is needed. There were other functions
> in eval.c there are also needed for lists and dicts, but I could copy them to
> if_lua as a workaround.
>
> If Bram accepts a patch and makes these functions not static and creates a
> eval.pro prototype, I would patch if_lua to avoid conflicts. It should be
> noted that these changes in eval.c would make Vim's API more amenable to
> language extensions and a tighter integration, as a thread some time ago
> requested.
>
> Cheers,
> Luis
>
> --
> Computers are useless. They can only give you answers.
> -- Pablo Picasso
>
> --
> Luis Carvalho (Kozure)
> lua -e 'print((("[email protected]"):gsub("(%u+%.)","")))'
There are some restrictions for making these functions non-static? By the way,
there were two more common functions in my if_python and if_lua, but AFAIR,
they were slightly different from eval.c so I copied them (without really
examining how significant the differences are).
--
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
