Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site terak.UUCP
Path: utzoo!utcs!lsuc!pesnta!hplabs!hao!noao!terak!doug
From: doug@terak.UUCP (Doug Pardee)
Newsgroups: net.works
Subject: Re: grisly grizzled programs
Message-ID: <379@terak.UUCP>
Date: Mon, 18-Feb-85 12:23:45 EST
Article-I.D.: terak.379
Posted: Mon Feb 18 12:23:45 1985
Date-Received: Wed, 20-Feb-85 08:43:36 EST
References: <596@topaz.ARPA> <372@terak.UUCP> <3284@umcp-cs.UUCP>
Organization: Terak Corporation, Scottsdale, AZ, USA
Lines: 18

> Ok, let's actually take this real example of "ls" bugs (4.2BSD manual):
> 
> 	Newline and tab are considered printing characters in file names.
> 
> Now seriously, how often do you find file names with newlines and tabs
> in them?  Has *anyone* ever *really wanted* ls to print \n or \t?

This misses the point.  The point is not whether or not it is a major
problem.

The point is that the problem has been known to exist for many years,
is absolutely trivial to fix, and yet *has never been fixed*.

This is in direct contradiction to a claim that (in general) programs
which were produced on-line are "more polished" than the programs
that used to be produced using batch methods.
-- 
Doug Pardee -- Terak Corp. -- !{hao,ihnp4,decvax}!noao!terak!doug