On 2/6/25 5:12 PM, Phi Debian wrote:
Again, may be it is just me, but the reading with the back and forth
reading and long distance jump in the docco to figure out how it works
looks complicated, but that's good enough, I can proceed :-)
This is one place where the info format, with its intern
On 2/6/25 5:08 PM, Phi Debian wrote:
I still don't know the impact (implication) of extdebug, does it impact
perf ?
The effects of extdebug are documented in the man page. Some of the
bookkeeping for BASH_ARGC and BASH_ARGV will have an effect on performance
versus not maintaining them, but mos
It was not obvious from the reading that it would work when trap is inside
the function but that is exactly what I need.
Again, may be it is just me, but the reading with the back and forth
reading and long distance jump in the docco to figure out how it works
looks complicated, but that's good en
I still don't know the impact (implication) of extdebug, does it impact
perf ?
On Thu, Feb 06, 2025 at 14:54:29 -0500, Chet Ramey wrote:
> On 2/6/25 12:59 PM, Greg Wooledge wrote:
>
> > If extdebug really does imply functrace, then that's missing from the
> > documentation. The rest appears to be working as intended.
>
> Look at item 5.
>
> extdebug
>
On 2/6/25 12:59 PM, Greg Wooledge wrote:
If extdebug really does imply functrace, then that's missing from the
documentation. The rest appears to be working as intended.
Look at item 5.
extdebug
If set at shell invocation, or in a shell startup file,
On Thu, Feb 06, 2025 at 18:41:14 +0100, Phi wrote:
> I find the docco for return [n] not easy to interpret. Here is what can be
> read.
>
>return [n]
> Stop executing a shell function or sourced file and
> return the value specified by n to its caller.
>
