coreutils/src/expr.c, branch v6.7 Mirror of https://https.git.savannah.gnu.org/git/coreutils.git/ https://git.shady.money/coreutils/atom?h=v6.7 2006-10-24T23:05:30Z * src/cat.c (infile): Add "const" to declaration. 2006-10-24T23:05:30Z Jim Meyering jim@meyering.net 2006-10-24T23:05:30Z urn:sha1:e81a82b74f44bfddce247d566617137725f11b19 * src/csplit.c (prefix): Likewise. * src/printf.c (cfcc_msg): Likewise. * src/tail.c (valid_file_spec): Likewise. * src/cut.c (cut_file): Likewise, for a parameter. * src/expr.c (str_value): Likewise. * src/fold.c (fold_file): Likewise. * src/pr.c (init_header): Likewise. * src/dircolors.c (dc_parse_stream): Likewise, for a local. * src/tr.c (make_printable_str): Likewise. * src/nl.c (body_type, header_type, footer_type, current_type): (separator_str, build_type_arg, nl_file): Likewise, for many. * src/paste.c (main): Don't assign a read-only string to 'optarg'. * src/tac.c (separator, tac_seekable, copy_to_temp): Likewise. (eval6): Fix buffer overrun, or bad performance, if 2006-09-11T04:56:43Z Paul Eggert eggert@cs.ucla.edu 2006-09-11T04:56:43Z urn:sha1:d28b0d4de83f21c85f273cbf8cba3f7b68e42ff5 substr's last operand is very large. Performance problem reported by Sebastian Kreft. (eval4): Detect overflow properly when multiplying INTMAX_MIN * -1. 2006-06-08T02:53:25Z Paul Eggert eggert@cs.ucla.edu 2006-06-08T02:53:25Z urn:sha1:cad27cdc2ea46ec401b71b76a92fcf3bc1d094e0 Don't claim x86 behavior is erroneous in a comment. 2006-06-07T05:58:57Z Paul Eggert eggert@cs.ucla.edu 2006-06-07T05:58:57Z urn:sha1:0eef2e1e8b40c36244311e4180fb5dd76ea50fa6 (integer_overflow): New function. 2006-06-07T05:52:27Z Paul Eggert eggert@cs.ucla.edu 2006-06-07T05:52:27Z urn:sha1:dea306fe784789b0d9b7f63cd53f3b492d3a691d (eval4, eval3): Check for integer overflow. Clear the RE_NO_EMPTY_RANGES re syntax option, as this is a less intrusive 2006-04-12T07:37:11Z Paul Eggert eggert@cs.ucla.edu 2006-04-12T07:37:11Z urn:sha1:7e17831f0a03acc9a92dcc73ed525ab2e61e706f change from the old (Emacs) behavior, and POSIX allows us to treat [z-a] as an empty range. (docolon): Set re_syntax_options to a value that is compatible with 2006-04-12T07:16:20Z Paul Eggert eggert@cs.ucla.edu 2006-04-12T07:16:20Z urn:sha1:110970f622b097df0ef3938e0982526022baeeb1 what POSIX requires. Also, don't let anchors match newline; this fixes an incompatibility with tradition and with POSIX. Don't warn about leading ^. POSIX says it is unspecified whether ^ is a special character, which means that implementations can either treat it as special or not, but either way a warning is not allowed (unless the regexp is otherwise invalid). Instead, anchor the expression but treat ^ as an anchor; this is the traditional behavior (e.g., Solaris 10). (eval4, eval3, eval2): Treat non-numeric args, division by zero, and the like as invalid expressions (exit status 2), not as failure of 'expr' (exit status 3). This is more consistent with how Solaris behaves. (docolon): Allocate and use a fastmap. 2006-04-11T00:50:56Z Paul Eggert eggert@cs.ucla.edu 2006-04-11T00:50:56Z urn:sha1:2a124564c75278f0a687205d9a58fdb4fed89096 Don't bother allocating a buffer. (docolon): Add IF_LINT check to avoid GCC warning. 2005-09-13T22:30:56Z Paul Eggert eggert@cs.ucla.edu 2005-09-13T22:30:56Z urn:sha1:360b98042fa20a4418371cb91ad0d881c6d3762d * src/expr.c (docolon): 64-bit regex fixes. 2005-09-09T21:08:51Z Paul Eggert eggert@cs.ucla.edu 2005-09-09T21:08:51Z urn:sha1:35155485bb3c31b06e3cea38773fb0c7379c8c72