> -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of Charles E. Campbell, Jr. > Sent: 16 January 2008 05:04 > To: [email protected] > Subject: Re: New features to vote on and sponsoring > > > I think it'd be a small thing -- but only Bram knows for sure. > > I'd like Decho (from my debugging plugin) to be able to report what > line/file/function it was called from so I can relate Decho output to > where it was generated. Something like the following would do the > trick: > > v:call_line -- would hold the line number (either the absolute line > number or like echoerr reports, function-relative) of what called the > current function > v:call_file -- would hold the name of the file (if absolute line number > is used for v:call_line) > v:call_function -- would hold the name of the calling function (if > function-relative line number is used for v:call_line) > > I'm afraid that I didn't see anything quite like that available. Its > like echoerr, but echoerr only need report where *it* was called. The > stuff above would probably necessitate recording what echoerr knows but > at the point of the call. I suppose these variable values would need > to > be placed on a stack to maintain validity when function calls a > function > calls a function, and then the deepest one returns. > > What'ch'all think? (my famous line before getting shot down)
Excellent suggestion IMHO, very useful, immediately usable. And it may not be all that hard to implement. ---Zdenek
smime.p7s
Description: S/MIME cryptographic signature
