From owner-cvs-all Thu Nov 1 12:45:55 2001 Delivered-To: cvs-all@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id B4CC537B407; Thu, 1 Nov 2001 12:45:48 -0800 (PST) Received: from winston.freebsd.org (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id fA1KjHf46303; Thu, 1 Nov 2001 12:45:17 -0800 (PST) (envelope-from jkh@winston.freebsd.org) To: Sheldon Hearn Cc: "David E. O'Brien" , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/boot/ficl/softwords softcore.awk In-Reply-To: Message from Sheldon Hearn of "Thu, 01 Nov 2001 21:41:26 +0200." <91831.1004643686@axl.seasidesoftware.co.za> Date: Thu, 01 Nov 2001 12:45:17 -0800 Message-ID: <46299.1004647517@winston.freebsd.org> From: Jordan Hubbard Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have to agree. As I already indicated to David on IRC, this change clearly wasn't as painless as anticipated and rather than run around bashing on other components in an attempt to bring the mountain to Mohammed we should simply go back to GNU awk *which worked fine* and save this change-over for a day when AT&T awk is actually POSIX compatible. Given all the far more important things we need to be focusing on right now, it is an almost incomprehensible waste of time to be fixing things that were not broken to begin with (and let's not get into the GPL vs BSD debate here - this is a functionality issue to which licensing issues take a definite back seat). - Jordan > > > On Thu, 01 Nov 2001 11:14:16 PST, "David E. O'Brien" wrote: > > > Modified files: > > sys/boot/ficl/softwords softcore.awk > > Log: > > Substitute "[:space:]" with the character constants it expands to. > > This was a silent 'failure' when using Bell-Labs awk. > > David, why are you taking this approach? Why are you worsening the > quality of our awk code [1] instead of ensuring that we have an awk > interpreter that adherers to standards? > > Can I suggest you take the approach I outline in another message, where > you reconnect gawk to the build as the system awk until such time as > these wrinkles have been ironed out properly? > > Ciao, > Sheldon. > > [1] In this case, the code becomes susceptible to cut-n-paste damage > that it was previously impervious to. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message