Date: Mon, 28 Jan 2002 10:44:42 +1030 From: Greg Lehey <grog@FreeBSD.org> To: Mike Barcroft <mike@FreeBSD.org> Cc: "Brian F. Feldman" <green@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/uuencode uuencode.1 src/usr.bin/uudecode uudecode.c Message-ID: <20020128104442.M72512@wantadilla.lemis.com> In-Reply-To: <20020127182308.D10222@espresso.q9media.com> References: <200201271821.g0RILN284192@freefall.freebsd.org> <200201272309.g0RN9R599282@green.bikeshed.org> <20020127182308.D10222@espresso.q9media.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, 27 January 2002 at 18:23:08 -0500, Mike Barcroft wrote: > Brian F. Feldman <green@FreeBSD.org> writes: >> Mike Barcroft <mike@FreeBSD.org> wrote: >>> mike 2002/01/27 10:21:23 PST >>> >>> Modified files: >>> usr.bin/uuencode uuencode.1 >>> usr.bin/uudecode uudecode.c >>> Log: >>> Add -o option (POSIX.1-2001) to uudecode(1). Deprecate the -p option >>> (which allows one to redirect output to stdout); `-o /dev/stdout' is >>> recommended instead. >>> >>> Submitted by: Joseph Mallett <jmallett@xMach.org> >>> MFC after: 2 weeks >> >> How about `-o -'? > > "In early drafts, the [-o outfile] option-argument allowed the use of > - to mean standard output. The symbol - has only been used previously > in IEEE Std 1003.1-2001 as a standard input indicator. The developers > of the standard did not wish to overload the meaning of - in this > manner. The /dev/stdout concept exists on most modern systems. The > /dev/stdout syntax does not refer to a new special file. It is just > a magic cookie to specify standard output." > --POSIX.1-2001 God, that's ugly. What was wrong with -p? Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020128104442.M72512>