Bot releases are hidden (Show)
Full Changelog: https://github.com/benhoyt/goawk/compare/v1.27.0...v1.28.0
Published by benhoyt 6 months ago
Full Changelog: https://github.com/benhoyt/goawk/compare/v1.26.0...v1.27.0
Published by benhoyt 8 months ago
Full Changelog: https://github.com/benhoyt/goawk/compare/v1.25.0...v1.26.0
Published by benhoyt about 1 year ago
This release includes several minor changes:
system()
and close()
for pipes more closely match Gawk's. Internal refactoring of the input and output stream implementation to make this happen. See issues #203 #204 #205 and thanks @juster!\u
Unicode string escape that's been added to onetrueawk and Gawk recently. #212Published by benhoyt over 1 year ago
This release contains several minor fixes and the addition of --csv
(it's an alias for -i csv
). This is for compatibility with onetrueawk and Gawk, which are both adding that option soon.
It also contains a minor backwards-incompatible change: in CSV input mode (-i csv
), the behaviour of the two-argument form of split()
now parses using CSV splitting, rather than FS. This is also in line with the upcoming --csv
feature of onetrueawk and Gawk. This is very unlikely to affect anyone, as CSV mode is relatively recent, and it seems unlikely that anyone is using the two-argument form of split()
in CSV mode in any case.
Full list of changes:
{ blocks }
with just semicolons in them in https://github.com/benhoyt/goawk/pull/192 -- thanks @raygard for the bug reportexit
without status code doesn't set exit code in https://github.com/benhoyt/goawk/pull/193 -- thanks @raygard for the bug reportsplit()
respect CSV input mode in https://github.com/benhoyt/goawk/pull/198
--csv
option, in line with upcoming AWK and Gawk feature in https://github.com/benhoyt/goawk/pull/199
--csv
in https://github.com/benhoyt/goawk/pull/200
Published by benhoyt over 1 year ago
This is a patch version that fixes panics when compiling AWK code that uses complex, mutually-recursive functions (fixed in PR #187). Thanks @xonixx for the test case.
Published by benhoyt over 1 year ago
This is patch release to fix a bug where mutually-recursive functions would cause an "undefined function" error in the resolver (PR #184). Thanks @xonixx for the bug report (#183).
Published by benhoyt over 1 year ago
This is a patch release that fixes a bug in 1.23.0 -- there was a bug that caused a panic in the resolver step with code like function f1(A) {} function f2(x, A) { x[0]; f1(a); f2(a) }
. Fixed in #178.
While we're at it, also fix a panic with certain obscure regexes (#179) and limit ARGC
to a reasonable maximum (#180).
All three of these issues were found by fuzzing: go test ./interp -fuzz=FuzzSource
Published by benhoyt over 1 year ago
This release adds a single new feature: support for length(array)
in addition to length(string)
(#176). Calling length()
on an array is quite useful and is supported by all other awk versions (onetrueawk, Gawk, mawk, busybox awk, frawk). In addition, it's been accepted for inclusion into POSIX, though not yet added to the main spec (which seems to take forever).
This release also includes a complete rewrite of the type resolver (#175). Before the code was quite messy and hard to read, now with the two passes I think it's easier to understand and work with. It was certainly easier to add the length(array)
feature with the rewritten resolver than before.
Published by benhoyt over 1 year ago
A fairly minor release, fixing some edge cases and adding support for nextfile
:
$++lvalue
not an error (#168)toString()
at runtime (#169)cond && var=value
and similar expressions (#170)(a)++b
parsing issue; pretty-print precedence (#172)nextfile
(#173)See full list of commits.
Published by benhoyt almost 2 years ago
Significant changes in this release:
-d
, -da
, and -dt
print to stdout and exit (https://github.com/benhoyt/goawk/pull/155). Thanks, @xonixx.Published by benhoyt over 2 years ago
New features and bug fixes (thanks @paulapatience for the reports):
Minor changes:
Published by benhoyt over 2 years ago
Notable changes in this release:
In other news, check out awk-demo, an amazing "old skool demo" written in AWK by @patsie75. It now works under GoAWK, at least on Linux. Clone that repo and run it with awk=goawk ./demo.sh
!
Thanks to @ko1nksm for several bug reports.
Published by benhoyt over 2 years ago
Relatively minor release with the following changes:
ExecuteContext
.huge.csv
, and adding explicit tests using ASCII and Unicode unit and record separators.awkgo
directory and code to a branch and removed it in the master branch; removed the unnecessary examples
directory.Published by benhoyt over 2 years ago
Minor test fixes, no change in functionality:
Published by benhoyt over 2 years ago
Now with proper CSV input and output support! For example, a simple example showing CSV input parsing and the new @"named-field"
syntax:
$ goawk -i csv -H '{ print @"Abbreviation" }' testdata/csv/states.csv
AL
AK
AZ
...
This feature was sponsored by the library of the University of Antwerp -- many thanks!
Published by benhoyt over 2 years ago
interp.New
... Execute
API to speed up and reduce allocations when executing the same program multiple times. https://github.com/benhoyt/goawk/pull/100
ExecuteContext
API to support timeout and cancellation. https://github.com/benhoyt/goawk/pull/103
x = "a" "," "b"
. https://github.com/benhoyt/goawk/pull/99
print
, printf
, sprintf()
, and field parsing. https://github.com/benhoyt/goawk/pull/102
Published by benhoyt over 2 years ago
This release adds no new features. It's a significant performance improvement due to switching the internals of the interpreter from a tree-walking interpreter to a bytecode compiler with a virtual machine interpreter.
Results show that it's 18% faster overall on microbenchmarks, 13% on more real-world benchmarks. It should be fully backwards compatible -- please file an issue if you find a regression!
Published by benhoyt over 2 years ago
This reverts the feature from v1.11.0 which changed the builtin functions length
, substr
, index
, and match
to use character indexes instead of byte indexes (as per the POSIX spec). The reason is because it changed those functions from O(1) to O(N), which created "accidentally quadratic" behavior in scripts that expected these functions to be O(1).
For example, @xonixx's grok.awk script on a relatively large JSON input file took about 1s in bytes mode (goawk -b
), but 8 minutes (!) in the new unicode char default mode. That's extremely problematic.
Like v1.11.0, this release is again a small breaking change, but once again shouldn't affect many scripts (it will again only affect scripts that use constant indexes for substr on non-ASCII strings). I hope not many people are using interp.Config.Bytes
or the goawk -b
option yet, as those are gone again. Seeing v1.11.0 was only introduced a few weeks ago, I think it's worth the breakage for a performance problem of this magnitude.
Fixes https://github.com/benhoyt/goawk/issues/93: "Major speed regression for gron.awk in goawk 1.11.0+".
Published by benhoyt almost 3 years ago
Support RS being multiple characters and regular expressions RS (#86), allowing significantly more powerful text processing. This is a Gawk extension to POSIX, which says, "If RS contains more than one character, the results are unspecified."