I actually found that using the function number in place of function
name works for :breakadd command. When I tried this first time, I used
breakadd incorrectly (used ":breakadd func 31" instead of ":breakadd
func 1 31").
However, the comment about not being able to find them or list them at
global scope still holds. If this is possible, I can enhance my
breakpts.vim script to take care of the numbered functions as
well. Please let me know if there is something that I am not finding.
--
Thanks,
Hari
On Wed, 21 Jun 2006 at 4:46pm, Hari Krishna Dara wrote:
>
> I can't figure out how to set breakpoints in numbered functions, and
> find it difficult to debug in general, using them. They are not listed
> in the :function output, and there may not be a global identifier to use
> in the :breakadd command (e.g., functions on a script local dictionary).
> It would also be nice if the stack trace that Vim reports has a
> reference to the original name of the function rather than the function
> number.
>
> Another strange thing about them is that if you get the string() value
> of the reference, it will give something like "function('31')", but if
> you pass '31' to function(), it will say invalid, so they can't be
> reached from a global scope.
>
> If the new :breakhere command worked on functions, it would have helped
> a bit, but it works only at the script level.
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
