Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 27 Jan 2002 18:23:08 -0500
From:      Mike Barcroft <mike@FreeBSD.org>
To:        "Brian F. Feldman" <green@FreeBSD.org>
Cc:        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:  <20020127182308.D10222@espresso.q9media.com>
In-Reply-To: <200201272309.g0RN9R599282@green.bikeshed.org>; from green@FreeBSD.org on Sun, Jan 27, 2002 at 06:09:27PM -0500
References:  <200201271821.g0RILN284192@freefall.freebsd.org> <200201272309.g0RN9R599282@green.bikeshed.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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

Best regards,
Mike Barcroft

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?20020127182308.D10222>