On 14/12/13 20:18, Bram Moolenaar wrote:
Andy Wokula wrote:
Bug: no nested autoloading within `=expr`
:h `=
,----[ autoload/air.vim ]-
| func! air#Fname()
| return beer#Fname()
| endfunc
`----
,----[ autoload/beer.vim ]-
| func! beer#Fname()
| return $TEMP.'/air-beer.txt'
| endfunc
`----
What happens if the filenames are reversed alphabetically, so that
the dependency appears in "air.vim" and the final function called is
from "beer.vim"? Could this particular bug just be a function of
module load order?
:sp `=air#Fname()`
Error detected while processing function air#Fname:
line 1:
E117: Unknown function: beer#Fname
E15: Invalid expression: beer#Fname()
"0" [New File]
I'll put it in the todo list.
Without some kind of C-style function prototyping mechanism
which specifies exactly which module a dependent function is in,
the act of having to cache all functions from all autoload modules
in memory simultaneously during VIM startup just for the purpose
of searching for autoload inter-dependencies could have drastic
negative effects on VIM startup resources and/or times.
--
--
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/groups/opt_out.
