Re: Debugging of dynamocally defined functions

["Bart Schaefer" <schaefer@candle.brasslantern.com>]

On Jul 9,  3:52pm, Peter Stephenson wrote:
} Subject: Re: Debugging of dynamocally defined functions
}
} I've discovered that bash simply gives 0 for line numbers in eval.  This
} (perl-like) behaviour of numbering eval's separately is probably more
} useful than that, at least.
}  
} I suspect the only way of finding out whether people prefer this behaviour
} is to commit it.  So I'll do that and produced 4.1.0-dev-1.

After playing with this for a few minutes I have the following observations:

In xtrace output the `eval' itself gets a line number before the commands
that it executes are numbered, so that's fine -- it's possible to track
the eval to a line in the calling function/file.

However, neither the value of %N nor that of %_ in PS4 changes to indicate
that you've entered a new line numbering scope; only %i changes.  For a
large `eval' that can be quite distracting.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net