From 2929813c4f89388272a8bc034b09e72c5bf4e9c7 Mon Sep 17 00:00:00 2001 From: Warner Losh Date: Wed, 21 Jul 2021 20:17:50 -0600 Subject: [PATCH] Revert "awk: Issue a warning for old hex behavior." This reverts commit acf9cf323f8d0c844ea4a0fedeb596871794a078. It warns about too many false positive cases. Sponsored by: Netflix --- contrib/one-true-awk/lib.c | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/contrib/one-true-awk/lib.c b/contrib/one-true-awk/lib.c index c2da07a7ba6..6bfe5e8eaad 100644 --- a/contrib/one-true-awk/lib.c +++ b/contrib/one-true-awk/lib.c @@ -798,16 +798,11 @@ bool is_valid_number(const char *s, bool trailing_stuff_ok, * where hex strings were treated as numbers in nawk the whole time it has been * in FreeBSD (since 2001). The POSIX 2001 through 2004 standards mandated this * behavior and the current standard allows it. Deviate from upstream by restoring - * the prior FreeBSD behavior, but warning that it differs. + * the prior FreeBSD behavior. */ +#if 0 // no hex floating point, sorry if (s[0] == '0' && tolower(s[1]) == 'x') -#ifdef __FreeBSD__ - { static int warned = 0; /* Only warn the first time */ - if (warned++ == 0) - WARNING("Script depends on old '0x' hex conversion behavior"); - } -#else return false; #endif