Date: Sun, 21 Jan 2024 04:25:26 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 276483] lang/mawk important type-related bug (fixed upstream) Message-ID: <bug-276483-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D276483 Bug ID: 276483 Summary: lang/mawk important type-related bug (fixed upstream) Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: wen@FreeBSD.org Reporter: daniel@belltech.it Flags: maintainer-feedback?(wen@FreeBSD.org) Assignee: wen@FreeBSD.org I'm pretty sure this bug was fixed in mawk 20230725, "improve scanner to so= me type-checks of arrays versus scalars by deferring this into the runtime execution (report by Rajeev V Pillai)." Here's a test for the bug: % echo|mawk 'function f(a){length(a)}{a[0]++;f(a)}' mawk: line 1: type error in arg(1) in call to f The problem is definitely upstream. This issue also occurs in the Debian and Ubuntu stock repos for mawk and is fixed on all OSes by compiling/installing more recent versions of mawk. (The test above works fine in newer mawk, awk, gawk, ports nawk, goawk, etc= .) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-276483-7788>