From owner-freebsd-bugs Wed Aug 25 9: 0:55 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 8271615099 for ; Wed, 25 Aug 1999 09:00:54 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id JAA04261; Wed, 25 Aug 1999 09:00:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Wed, 25 Aug 1999 09:00:01 -0700 (PDT) Message-Id: <199908251600.JAA04261@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: James Howard Subject: Re: bin/13364: Patch to wc(1) for Unix 98 compliance. Reply-To: James Howard Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/13364; it has been noted by GNATS. From: James Howard To: Sheldon Hearn Cc: freebsd-gnats-submit@freebsd.org Subject: Re: bin/13364: Patch to wc(1) for Unix 98 compliance. Date: Wed, 25 Aug 1999 11:53:29 -0400 (EDT) On Wed, 25 Aug 1999, Sheldon Hearn wrote: > Not sure how far away it is. I'm almost sure _someone_ is working on it. > I just know that I've been shot down a couple of times for making things > worse for that fateful day. :-) Okay, I looked at this. It will be broken, sort of, until wchar_t supporting functions are added. Then I don't think the change will be that big. Basically, you'll add another variable. Then break apart -c and -m. One will read a byte, the other a character. > Hardly. I'm just passing on what I've learned over the last few months. > Remember, this is _peer_ review. ;-) It was comment structure. If I had my way, there would be no comments at all :) Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message