12a55deb1SDavid E. O'Brien/**************************************************************** 22a55deb1SDavid E. O'BrienCopyright (C) Lucent Technologies 1997 32a55deb1SDavid E. O'BrienAll Rights Reserved 42a55deb1SDavid E. O'Brien 52a55deb1SDavid E. O'BrienPermission to use, copy, modify, and distribute this software and 62a55deb1SDavid E. O'Brienits documentation for any purpose and without fee is hereby 72a55deb1SDavid E. O'Briengranted, provided that the above copyright notice appear in all 82a55deb1SDavid E. O'Briencopies and that both that the copyright notice and this 92a55deb1SDavid E. O'Brienpermission notice and warranty disclaimer appear in supporting 102a55deb1SDavid E. O'Briendocumentation, and that the name Lucent Technologies or any of 112a55deb1SDavid E. O'Brienits entities not be used in advertising or publicity pertaining 122a55deb1SDavid E. O'Briento distribution of the software without specific, written prior 132a55deb1SDavid E. O'Brienpermission. 142a55deb1SDavid E. O'Brien 152a55deb1SDavid E. O'BrienLUCENT DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, 162a55deb1SDavid E. O'BrienINCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. 172a55deb1SDavid E. O'BrienIN NO EVENT SHALL LUCENT OR ANY OF ITS ENTITIES BE LIABLE FOR ANY 182a55deb1SDavid E. O'BrienSPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES 192a55deb1SDavid E. O'BrienWHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER 202a55deb1SDavid E. O'BrienIN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, 212a55deb1SDavid E. O'BrienARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF 222a55deb1SDavid E. O'BrienTHIS SOFTWARE. 232a55deb1SDavid E. O'Brien****************************************************************/ 242a55deb1SDavid E. O'Brien 25*f32a6403SWarner LoshThis file lists all bug fixes, changes, etc., made since the 26*f32a6403SWarner Loshsecond edition of the AWK book was published in September 2023. 272a55deb1SDavid E. O'Brien 28*f32a6403SWarner LoshJan 22, 2024: 29*f32a6403SWarner Losh Restore the ability to compile with g++. Thanks to 30b2376a5fSWarner Losh Arnold Robbins. 31f39dd6a9SWarner Losh 32*f32a6403SWarner LoshDec 24, 2023: 33*f32a6403SWarner Losh Matchop dereference after free problem fix when the first 34*f32a6403SWarner Losh argument is a function call. Thanks to Oguz Ismail Uysal. 35*f32a6403SWarner Losh Fix inconsistent handling of --csv and FS set in the 36*f32a6403SWarner Losh command line. Thanks to Wilbert van der Poel. 37*f32a6403SWarner Losh Casting changes to int for is* functions. 38f39dd6a9SWarner Losh 39*f32a6403SWarner LoshNov 27, 2023: 40*f32a6403SWarner Losh Fix exit status of system on MacOS. Update to REGRESS. 41b2376a5fSWarner Losh Thanks to Arnold Robbins. 42*f32a6403SWarner Losh Fix inconsistent handling of -F and --csv, and loss of csv 43*f32a6403SWarner Losh mode when FS is set. 44b2376a5fSWarner Losh 45*f32a6403SWarner LoshNov 24, 2023: 46*f32a6403SWarner Losh Fix issue #199: gototab improvements to dynamically resize the 47*f32a6403SWarner Losh table, qsort and bsearch to improve the lookup speed as the 48*f32a6403SWarner Losh table gets larger for multibyte input. Thanks to Arnold Robbins. 49b2376a5fSWarner Losh 50*f32a6403SWarner LoshNov 23, 2023: 51*f32a6403SWarner Losh Fix Issue #169, related to escape sequences in strings. 52*f32a6403SWarner Losh Thanks to Github user rajeevvp. 53*f32a6403SWarner Losh Fix Issue #147, reported by Github user drawkula, and fixed 54*f32a6403SWarner Losh by Miguel Pineiro Jr. 55b2376a5fSWarner Losh 56*f32a6403SWarner LoshNov 20, 2023: 57*f32a6403SWarner Losh Rewrite of fnematch to fix a number of issues, including 58*f32a6403SWarner Losh extraneous output, out-of-bounds access, number of bytes 59*f32a6403SWarner Losh to push back after a failed match etc. 60*f32a6403SWarner Losh Thanks to Miguel Pineiro Jr. 61b2376a5fSWarner Losh 62*f32a6403SWarner LoshNov 15, 2023: 63*f32a6403SWarner Losh Man page edit, regression test fixes. Thanks to Arnold Robbins 64*f32a6403SWarner Losh Consolidation of sub and gsub into dosub, removing duplicate 65*f32a6403SWarner Losh code. Thanks to Miguel Pineiro Jr. 66*f32a6403SWarner Losh gcc replaced with cc everywhere. 67b2376a5fSWarner Losh 68*f32a6403SWarner LoshOct 30, 2023: 69*f32a6403SWarner Losh Multiple fixes and a minor code cleanup. 70*f32a6403SWarner Losh Disabled utf-8 for non-multibyte locales, such as C or POSIX. 71*f32a6403SWarner Losh Fixed a bad char * cast that causes incorrect results on big-endian 72*f32a6403SWarner Losh systems. Also fixed an out-of-bounds read for empty CCL. 73*f32a6403SWarner Losh Fixed a buffer overflow in substr with utf-8 strings. 74*f32a6403SWarner Losh Many thanks to Todd C Miller. 75b2376a5fSWarner Losh 76*f32a6403SWarner LoshSep 24, 2023: 77*f32a6403SWarner Losh fnematch and getrune have been overhauled to solve issues around 78*f32a6403SWarner Losh unicode FS and RS. Also fixed gsub null match issue with unicode. 79*f32a6403SWarner Losh Big thanks to Arnold Robbins. 80b2376a5fSWarner Losh 81*f32a6403SWarner LoshSep 12, 2023: 82*f32a6403SWarner Losh Fixed a length error in u8_byte2char that set RSTART to 83*f32a6403SWarner Losh incorrect (cannot happen) value for EOL match(str, /$/). 84b2376a5fSWarner Losh 85b2376a5fSWarner Losh 86*f32a6403SWarner Losh----------------------------------------------------------------- 87b2376a5fSWarner Losh 88*f32a6403SWarner Losh[This entry is a summary, not a precise list of changes.] 89b2376a5fSWarner Losh 90*f32a6403SWarner Losh Added --csv option to enable processing of comma-separated 91*f32a6403SWarner Losh values inputs. When --csv is enabled, fields are separated 92*f32a6403SWarner Losh by commas, fields may be quoted with " double quotes, fields 93*f32a6403SWarner Losh may contain embedded newlines. 94b2376a5fSWarner Losh 95*f32a6403SWarner Losh If no explicit separator argument is provided, split() uses 96*f32a6403SWarner Losh the setting of --csv to determine how fields are split. 97b2376a5fSWarner Losh 98*f32a6403SWarner Losh Strings may now contain UTF-8 code points (not necessarily 99*f32a6403SWarner Losh characters). Functions that operate on characters, like 100*f32a6403SWarner Losh length, substr, index, match, etc., use UTF-8, so the length 101*f32a6403SWarner Losh of a string of 3 emojis is 3, not 12 as it would be if bytes 102*f32a6403SWarner Losh were counted. 103b2376a5fSWarner Losh 104*f32a6403SWarner Losh Regular expressions are processed as UTF-8. 105b2376a5fSWarner Losh 106*f32a6403SWarner Losh Unicode literals can be written as \u followed by one 107*f32a6403SWarner Losh to eight hexadecimal digits. These may appear in strings and 108*f32a6403SWarner Losh regular expressions. 109