home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!uunet!not-for-mail
- From: preece@urbana.mcd.mot.com (Scott E. Preece)
- Newsgroups: comp.std.unix
- Subject: Re: Report on POSIX.2: Shell and Utilities
- Date: 14 Sep 1992 11:55:06 -0700
- Organization: Motorola MCG, Urbana Design Center
- Lines: 25
- Sender: sef@ftp.UU.NET
- Approved: sef@ftp.uucp (Moderator, Sean Eric Fagan)
- Message-ID: <192n6aINNlt2@ftp.UU.NET>
- References: <18lqglINN992@ftp.UU.NET> <18u2i5INNo7e@ftp.UU.NET> <190k6vINN5g9@ftp.UU.NET>
- NNTP-Posting-Host: ftp.uu.net
- X-Submissions: std-unix@uunet.uu.net
-
- Submitted-by: preece@urbana.mcd.mot.com (Scott E. Preece)
-
- In article <190k6vINN5g9@ftp.UU.NET> brnstnd@KRAMDEN.ACF.NYU.EDU (D. J. Bernstein) writes:
- > I wish POSIX would stop shooting off into the cosmos, come back to
- > earth, and spend some time documenting what UNIX systems actually *do*.
-
- Funny, the POSIX meetings I've been to have tended to involve a lot of
- discussion of existing practice and a lot of drudging through existing
- documentation and rehashing it in the dullest possible language. What
- that drudging has generally led to is a realization that none of the
- existing documentation specifies *anything* completely enough and that
- every vendor's UNIX system is different. So you have to write a
- standard that specifies things nobody specified before and you have to
- try to merge different versions of the same functionality. And if
- you're a responsible engineer, you have to resist standardizing bad
- practice just because it is existing practice.
-
- scott
- --
- scott preece
- motorola/mcg urbana design center 1101 e. university, urbana, il 61801
- uucp: uunet!uiucuxc!udc!preece, arpa: preece@urbana.mcd.mot.com
- phone: 217-384-8589 fax: 217-384-8550
-
- Volume-Number: Volume 29, Number 35
-