[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: print: unexpected gawk's behaviour in case indirect function call
From: |
Denis Shirokov |
Subject: |
Re: print: unexpected gawk's behaviour in case indirect function call |
Date: |
Wed, 2 Feb 2022 15:23:30 +0200 |
the update step to reproduce script is followed:
BEGIN{
f = "match"
print "INDIRECT: " @f( a, b )
}
2022-02-02 15:16 GMT+02:00, Denis Shirokov <cosmogen@gmail.com>:
> Hi Gawk Team!
>
> i found strange gawk's behaviour that is completely makes me crazy
>
> example:
>
> BEGIN{
>
> print "DIRECT: " match( a, b )
>
>
> f = "match"
>
> print "INDIRECT: " @f( a, b )
>
>
> print "END" }
>
> output:
>
> D:\CPU\DEV\PROJECT\XASM>gawk -f ./a.txt
> DIRECT: 1
> match1
> < 'match' ??? wtf?
> END
>
> it's looks like it's lost leading "INDIRECT: " string and then outputs
> content of the
> globvar `f: "match" and THEN indirectly call built-in match() function
> and output it's
> result.
>
> please note that this behaviour was found while reporting about
> another gawk issue that's will be reported soon. the provided example
> is from there,
>
> Windows 10(x64)
> GNU Awk 5.1.1, API: 3.1 (GNU MPFR 4.0.2, GNU MP 6.1.2)
>
> Kind Regards
> Denis
>
- print: unexpected gawk's behaviour in case indirect function call, Denis Shirokov, 2022/02/02
- Re: print: unexpected gawk's behaviour in case indirect function call,
Denis Shirokov <=
- Re: print: unexpected gawk's behaviour in case indirect function call, Ed Morton, 2022/02/02
- Re: print: unexpected gawk's behaviour in case indirect function call, Neil R. Ormos, 2022/02/02
- Re: print: unexpected gawk's behaviour in case indirect function call, Denis Shirokov, 2022/02/03
- Re: print: unexpected gawk's behaviour in case indirect function call, arnold, 2022/02/03
- Re: print: unexpected gawk's behaviour in case indirect function call, arnold, 2022/02/07