Date: Tue, 03 Jun 2008 16:15:21 +0200 From: Kris Kennaway <kris@FreeBSD.org> To: Coleman Kane <cokane@FreeBSD.org> Cc: src-committers@FreeBSD.org, jhb@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org, stefanf@FreeBSD.org, marcus@marcuscom.com, "M. Warner Losh" <imp@bsdimp.com> Subject: Re: cvs commit: src/bin/sh expand.c parser.c parser.h Message-ID: <484551F9.9070300@FreeBSD.org> In-Reply-To: <1212501946.15220.1.camel@localhost> References: <1212440845.18384.49.camel@shumai.marcuscom.com> <20080602.204014.-222576415.imp@bsdimp.com> <1212461214.18384.83.camel@shumai.marcuscom.com> <20080602.213239.-861051005.imp@bsdimp.com> <1212501946.15220.1.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
Coleman Kane wrote: > If we chose to do that, then I'd also suggest a compile flag to turn on > "strict POSIX compliance". Then, perhaps some ports-auto-build-box > somewhere could generate a report of the configure scripts that do such > things, and could be used to nag them into fixing this problem. This could certainly be done, but the requirement is the set of developers to process the output. > Maybe someone should nag the bash developers... The bash developers have taken pride in how they have mangled their shell to support C-like syntax. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?484551F9.9070300>