Date: Tue, 3 Jun 2008 13:59:09 +0200 From: Joerg Sonnenberger <joerg@britannica.bec.de> To: cvs-src@freebsd.org Subject: Re: cvs commit: src/bin/sh expand.c parser.c parser.h Message-ID: <20080603115909.GB1707@britannica.bec.de> In-Reply-To: <200806021445.15974.jhb@freebsd.org> References: <200805151955.m4FJtRMb099378@repoman.freebsd.org> <200806021445.15974.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 02, 2008 at 02:45:15PM -0400, John Baldwin wrote: > Specifically note the "==" passed to test(1). POSIX says this should be "=", > and that's all our test(1) implements. The bash manpage for the builtin-test > command says: > > string1 == string2 > True if the strings are equal. = may be used in place of == for > strict POSIX compliance. What is even more annoying about this is that it is a BASHism, not a GNUism. The test from coreutils doesn't understand == either. Joerg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080603115909.GB1707>