Re: print: unexpected gawk's behaviour in case indirect function call

[arnold]

Hi.

Reports about different kinds of failures in a previous version are
not of interest.  I will fix issues in the current code, but I
am not worried about prior versions.

Thanks anyway,

Arnold

Denis Shirokov <cosmogen@gmail.com> wrote:

> also:
>
> for Gawk 5.1.0
>
>
> BEGIN{
>
>       f = "match"
>
>       print "INDIRECT: " @f( a, b )
>
>  }
>
>
> Assertion failed: r->valref > 0, file awk.h, line 1267
>
> do not reproducible with Gawk 5.1.1
>
> best regards
> Denis
>
> 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
> >