You do realize that there are no "nested functions" in bash, right?
Graycat, talk to me on Libera if you really doubt my understanding.
All functions exist in a single, global function namespace.
>
> unicorn:~$ bash
> unicorn:~$ f() { g() { echo I am g; }; }
> unicorn:~$ f
> unicorn:~$ type g
>
iner ==> infer sorry about typo's
Hum, may be I was over optimistic regarding alloca(), it seems it core
dumps as well :-), i.e never return NULL.
I was mentioning alloca() because I use to do my own stacksize check using
getrlimit() and getting the max stack size, and measuring the distance
between the stack_base and the recursio
On Tue, Oct 11, 2022 at 7:23 AM Martin D Kealey
wrote:
>
> 4) compile globs into state machines, the same way that regexes get
> compiled, so that they can be matched without needing any recursion.
>
> -Martin
>
Do you mean the NFA colud trade recursion for malloc()'d backtracking point
record?
On Mon, Oct 10, 2022 at 9:08 PM Chet Ramey wrote:
> That's not the point. The point is that shell pattern matching is used in
> contexts other than filename globbing, and the shell shouldn't broadly
> impose a filename-only restriction on those uses.
>
> Chet
>
Ok got it, I was confused because
On Sun, 9 Oct 2022 at 18:07, Phi Debian wrote:
> I was looking at a bug on ksh93 that is "core dumps doing glob pattern on
> long string" and it happen that bash
> suffer the same.
>
> $ [[ $(printf '%010d' 0) == +(0) ]]
>
> I see 3 way of fixing this
>
> 1) [...] string should be limited to
On 10/10/22 12:59 PM, Phi Debian wrote:
Ok, I agry that PATH_MAX should not be considered, because not defined
every where (OS's)
That's not the point. The point is that shell pattern matching is used in
contexts other than filename globbing, and the shell shouldn't broadly
impose a filename
On 10/9/22 11:32 AM, Kirill Elagin wrote:
Hi,
I think the execute_cmd.c change here
(https://git.savannah.gnu.org/cgit/bash.git/commit/?h=devel&id=1fff64acdc5709cdc213f0143f1b8169fdf68a39)
made things worse, not better. I don’t know what the original report
that prompted this change was though,
Ok, I agry that PATH_MAX should not be considered, because not defined
every where (OS's)
If you decide a limit let me know I would use the same for ksh93 :)
for the time being we core dump :)
Cheers.
On 10/10/22 2:38 AM, konsolebox wrote:
This doesn't look right to me:
# export BASH_ARGV0=fdsafasfas
# bash
# echo "$BASH_ARGV0|$0"
fdsafasfas|fdsafasfas
It's fine. If someone wants to set $0 when the shell starts, this is a way
to do it.
I added this back in 2019 as the result of a user requ
On 10/9/22 4:07 AM, Phi Debian wrote:
I was looking at a bug on ksh93 that is
"core dumps doing glob pattern on long string" and it happen that bash
suffer the same.
$ [[ $(printf '%010d' 0) == +(0) ]]
I see 3 way of fixing this
1) [[ string == pattern ]] is for glob pattern, so string sh
On 10/8/22 9:09 AM, Koichi Murase wrote:
Thank you for your reply and sorry for the late reply.
2022年10月4日(火) 0:56 Chet Ramey :
I expect the same behavior of `f1' and `f2' as far as there are no
background jobs.
Why? f2 calls `jobs', and so requests information in a particular format,
which m
12 matches
Mail list logo
