Date: Sun, 18 Jul 2021 16:04:24 -0700 From: Simon J. Gerraty via freebsd-arch <freebsd-arch@FreeBSD.org> To: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> Cc: Stefan Esser <se@FreeBSD.org>, Warner Losh <imp@bsdimp.com>, "freebsd-arch@freebsd.org" <freebsd-arch@FreeBSD.org>, <sjg@juniper.net> Subject: Re: FreeBSD awk behavior change proposal Message-ID: <56161.1626649464@kaos.jnpr.net> In-Reply-To: <202107101222.16ACM5Sb045675@gndrsh.dnsmgr.net> References: <202107101222.16ACM5Sb045675@gndrsh.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Rodney W. Grimes <freebsd-rwg@gndrsh.dnsmgr.net> wrote: > My concers are/were along the lines that awk was explicitly > setting or actually ignoring the users LC, what happens if > some user WANTS to build a port using some other locale, could > that lead to bad awk results, and a failed build. In practical terms a port which behaves differently based on LOCALE would be considered broken no? My experience is when tools start honoring LOCALE etc, the only path to retain consistent behavior is to override. eg. want to know if a pid is valid in a shell script? case "`LANG=C LC_ALL=C kill -0 $pid`" in *:*such*p*) return 1;; # not valid *) return 0;; # valid esac avoids portability headaches. --sjg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56161.1626649464>