Ingo Karkat wrote:
> Me, too. The following used to work:
>
> fun! Foo()
> endfun
> let g:Foo = function('Foo')
>
> After 7.4.264, I get:
> " E705: Variable name conflicts with existing function: g:Foo
That is correct. Previously Foo() and g:Foo were different names, which
is wrong. Both refer to the same function.
> In general, I do welcome the introduced restrictions, though, I've found
> a place where I attempted to define a buffer-local function (fun!
> b:Foo()); this is now correctly flagged with E128.
Right. So the problem is that users have been using wrong function
names, and they did work. Now they are flagged as errors, which may
break some scripts.
The question is: Is it acceptable to expect users to fix those scripts,
or do we need to be lenient. A possible way is to add an option to
allow the wrong names. That's not a nice solution though, it hides the
actual problem.
--
Where do you want to crash today?
/// 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.
